System and methods for IP and VoIP device location determination

ABSTRACT

A method and system for precise position determination of general Internet Protocol (IP) network-connected devices. A method enables use of remote intelligence located at strategic network points to distribute relevant assistance data to IP devices with embedded receivers. Assistance is tailored to provide physical timing, frequency and real time signal status data using general broad band communication protocols. Relevant assistance data enables several complementary forms of signal processing gain critical to acquire and measure weakened or distorted in-building Global Navigation Satellite Services (GNSS) signals and to ultimately extract corresponding pseudo-range time components. A method to assemble sets of GNSS measurements that are observed over long periods of time while using standard satellite navigation methods, and once compiled, convert using standard methods each pseudo-range into usable path distances used to calculate a precise geographic position to a known degree of accuracy.

RELATED APPLICATIONS

This application claims priority from U.S. Provisional PatentApplication No. 60/680,190, filed May 12, 2005, entitled “iPosi Receiverfor Deep In-Building Signal Acquisition and GPS Pseudorange Capture,”the entire disclosure of which is incorporated by reference herein.

FIELD OF THE INVENTION

The present invention relates to systems for determining positions ofnetwork-attached devices in general and, in particular, for determiningpositions of devices connected to asynchronous networks and capable ofreceiving signals from Global Navigation Satellite Services (GNSS). Theinvention has particular application for determining positions of VoiceOver Internet Protocol (VoIP) devices connected to the Internet andcapable of receiving signals from the Global Positioning System (GPS).

BACKGROUND OF THE INVENTION

Global satellite navigation fulfills pervasive needs. Initially aservice for military and general aviation, Global Navigation SatelliteServices (GNSS) are expanding into many commercial and consumer productsfor applications ranging from casual to emergency services. Morerecently cellular phones have been developed that provide location basedservice applications and, in response to government requirements,emergency caller location services. The preponderance of these servicesis enabled by the US Air Force managed Global Positioning System (GPS).GPS is now or may soon be joined by several additional GNSS systemsincluding: Glonass (Russia), Galileo (European Space Agency) and QZSS(Japan). Cellular phone embedded GPS uses the cellular network as anassistance tool to forward current and predicted satellite orbitalparameter data to reduce the satellite signal search burden. This isuseful in ordinary phones that are equipped with chip-scale GPSreceivers that can use other signal processing, RF and computationalprocessing elements already inside these phones. The assistance methodprovides a substantial reduction in the time to initially acquire aposition fix by reducing the search field and by limiting the search towhere the overhead satellites are known to occupy distinct frequency andcode-phase zones of the signal search area. Mobile assisted GPS is thebackbone of positioning devices for Emergency 9-1-1 (E911) calls in theUnited States, and in 2005 supported an estimated time-urgent 100million E911 calls.

The utility of exact positioning cannot be overestimated when safety andsecurity is involved, and several governments now seek precise locationfor their respective countries' public communication and first-responderinfrastructure. At the same time that they seek this service, theirpublic communication infrastructure is shifting rapidly from fixedcircuit switched networks to Voice Over Internet Protocol (VoIP)networks. However, current IP networks are not geo-referenced to eitherintelligently route or pinpoint the location of E911 callers. Further,VoIP is a service that has portable or nomadic connectivity. VoIPservice providers are also no longer 100% facilities based providers.Therefore, VoIP is often hosted, that is supported technically, acrossfacilities with no linkage administratively between the facility oraccess and the VoIP service providers. Additionally, no single currentprovider has a network plant with a reach of VoIP service that coversall the geographical points at which VoIP subscribers connect.

To support the ability to locate the VoIP-enabled emergency caller,proposals have been offered to manually survey or map the underlyingfixed plant assets. This method may have limited effectiveness, wouldrequire service suspension if the user connects at a new location, andwould incur additional mapping costs when the user connects at a newlocation. Other proposals to use parasitic methods by acquiring andmapping signals such as WiFi or TV broadcast signals. Some have proposedentirely new, dedicated signals, using separate spectrum andinfrastructure, deployed for the sole purpose of locating objects, petsor people. A common belief or premise of these proposals is GPS cannotoperate successfully to reach receiver points located inside buildingsand homes due to limits of effective satellite signal sensitivity. Thislimitation is often attributed to the fact that the satellites are faraway and have comparatively limited transmission power.

SUMMARY OF THE INVENTION

The present invention relates to systems for determining positions ofnetwork-attached devices and associated methodologies. In particular, anautomated position determination system is provided, which when addedinside host equipment operates over standards-based broadbandcommunication networks, that is, it uses those networks in unmodifiedform. One aspect is that the systems may function over asynchronousnetworks, including delivery of precise time and frequency via packetsignaling which provides the foundation for acquiring weak GNSS signalsvirtually anywhere, automatically and inexpensively.

One embodiment of the present invention provides a method to preciselyposition network-connected devices using a specific configuration ofspecialized servers, which in turn serve a multitude of inexpensive,standardized, position determination edge devices with embeddedreceivers. These receivers readily embed as silicon components or arefully die-level integrated into a diverse array of commerciallyavailable VoIP and IP devices. Consistent with the service feature ofVoIP, these devices may be readily moved, and may operate as “nomadic”changing between portable and fixed usage behavior. It is thereforedesirable to seamlessly maintain an updated location should consumersmove the device to different places. These devices generally attach tonetworks that do not have a common, precise time and/or frequencyreference. When called for by control logic and in response to aprogrammed set of conditions, each remote receiver may provide andtransfer network messages using conventional IP connection and/or packetprotocols. Furthermore, these devices interact using conventionalstreaming packets that provide valuable signals to disseminate time andfrequency, which enable remote receivers to align local frequency andtime and then capture positioning system signals such as targetnavigation satellite signals. These signals provide range measurements.The signals are then encoded and sent back to a central server, and oncesatisfying certain accuracy criteria, are then transferred into anindustry standard Location Information Server (LIS) database as part ofmodern VoIP and IP device location management standards or governmentregulatory mandates.

Aspects of the present invention provide for extended receiversensitivity, relative to known commercial GPS systems, in order toacquire weak in-building GNSS signals. Additional aspects are operableto extend the coherent signal integration time, relative to knowncommercial GPS systems, when signal conditions warrant thoughacquisition and measurement of single GNSS signal acquisitions eventswhich are later clock-corrected to form a position assembled fromtime-spread observations. Still further aspects use knowledge of commonrouter connections to combine nearby receiver measurements leading toimproved building address position accuracy.

Accordingly, in accordance with one aspect of the present invention, amethod for determining the position of a device connected to a computernetwork relative to a fixed coordinate system is provided. Embodimentsof this aspect may include various types of network-attached devices.Such devices may include personal computers and devices with Voice OverData Network (VODN) capabilities. In one embodiment the device is a VoIPphone. The VoIP phone may be attached to any network connectionincluding an ethernet connection or a DSL or cable connection. VoIPphones are generally stand-alone units that function similar totraditional phones attached to the Public Switched Telephone Network(PSTN) and communicate over asynchronous Internet Protocol (IP) networkssuch as the Internet. As to the network to which the device is attached,it may be any computer network including asynchronous networks that useindustry-standard packet communication protocols and do not supply timeor frequency references for attached devices. Such networks may includethe public Internet, or private Intranets such as those operated bycorporations, institutions or governments. This system may be applied tosegments of an interconnected network such as local area networks.

In another embodiment, the device whose location is to be determined maybe connected to the network through a wireless access point. In thisconfiguration, the device may refer to the location of the wirelessaccess point as a sufficiently precise location. This is particularlyapplicable to short range wireless devices, such as 802.11b deviceswhere the device is generally well under 100 meters from the servingaccess point. In an alternate embodiment, the device or wireless accesspoint may be operable to directly determine the device's locationrelative to the wireless access point. Under these circumstances, thedevice may be located based on the combination of the wireless accesspoint position and the location of the device relative to the wirelessaccess point.

In accordance with another aspect, a method is provided for estimatingthe position of a device relative to a fixed coordinate system throughcommunications over a computer network. The communications may bebetween the device to be located and a model server. The connectionbetween the network and the device may be a broadband connection, andmay be operable to transfer data at a rate of at least about 128kilobits per second (kbps) bidirectionally. The fixed coordinate systemmay be a standard system using latitudes and longitudes to fix aposition such as those generally used by GNSS systems. Exemplary GNSSsystems include GPS (United States) and Glonass (Russia), and currentlyplanned systems Galileo (European Space Agency) and QZSS (Japan).

In accordance with another aspect, the communications route between themodel server and the device may serve to help estimate a position of thedevice. For example, the device or the model server may initiate an IPtrace route for the communication path between the device and the modelserver. This IP trace route would provide information as to intermediaterouters in that communication path. This information may then be used bythe model server to make an estimation of the device's location based ona known position of routers encountered in the communication path. Theknowledge of positions of routers may be obtained by accessing adatabase containing such information. The database may have beendeveloped by gathering data from previous device location efforts. Thedatabase may be a commercial database which the model server accessesthrough a network connection. This method will generally be able toestimate the position of the device to within 10-100 km of the device'sactual position. If the IP trace route reveals a router to which thedevice is directly connected, where that router's position is known theaccuracy of the estimate can be reliably assumed to be within 10-30 kmin most urban and suburban areas. The system may tolerate up to a 100 kmaccuracy but any higher accuracy will enhance convergence time of thesignal acquisition process since the estimated parameters will be closerto the true values of the incoming GNSS signals. In another possiblescenario, the IP trace route may reveal that the device whose positionis to be determined is connected to the same router as a device whoseposition has previously been determined. In the case of many officebuildings, association of shared routers will provide an initialposition estimate to within several hundred meters. In this regard, itis an aspect of the present invention, that as more and more devices arelocated through the present methods, initial estimates of positions maybe enhanced due to common router connections.

In accordance with another aspect, the device whose position is to bedetermined may obtain data over a computer networking regarding signalcharacteristics of a positioning system relative to an estimatedlocation of the device. The positioning system may be a terrestrialbased system, for example a system comprised of transmission towerstransmitting signals which can then be used to determine a location, ora GNSS system. The signal characteristics of the positioning systemrelative to the estimated location of the device may be determined by amodel server and transferred to the device over a network connection.The signal characteristics may include such characteristics as thesignal frequency calculated to be incident on the estimated location,signal code phase, signal frequency rate of change over time, navigationcode bit state, and bit time transition, or other usable carrier signaland modulation characteristics. The model server may determine thesecharacteristics by accessing known providers of such characteristics orby calculating the signal characteristics. The signal characteristicsmay take into account atmospheric and motion related factors, which mayinfluence the characteristics of the signal incident on the estimatedlocation. For example, the signal characteristics may take into accountDoppler carrier frequency shifting effects.

In accordance with yet another aspect, a peering point server may beprovided that is operable to communicate with the device over thecomputer network wherein the peering point server is synchronized withor calibrated to relevant time references of the signal structure of thesatellite positioning system. The peering point server may maintaincalibration with the positioning system through the reception of signalsfrom the positioning system. In the embodiment where the positioningsystem is the GPS, the peering point server may receive multiple GPSsignals that would enable the peering point server to maintainsynchronization with the GPS system. To facilitate this, peering pointservers may have sophisticated components (relative to consumer GPSdevices) and remotely mounted antennae (for clear viewing ofsatellites). The peering point servers may also be provided with highlyaccurate internal timing references to maintain or backup precisesynchronization with the positioning system. This may be used as aprimary system or as a backup system for when positioning system signalsare not available. The internal timing reference, for example, may be anatomic clock and its accuracy may be better than 100 parts per billionas measured against the time reference of the positioning system. In oneembodiment, a plurality of peering point servers may be locatedthroughout the region where devices are to be located. In anotherembodiment, the peering point servers may contain atmospheric pressuresensors. In this embodiment, since the peering point servers would be ata known altitude, the atmospheric pressure sensors in the peering pointservers could be used to determine local atmospheric pressure whichcould then be used to calibrate barometric altimeters that may belocated in nearby devices whose precise locations are to be determined.This would lead to the determination of the precise altitude of thedevices whose locations are to be determined, which would aid in thelocation determination process.

In accordance with yet another aspect, a peering point server may beprovided that is operable to communicate with a device over a computernetwork wherein the communications between the peering point server andthe device may be used to estimate a position of the device in theabsence of the device receiving any signals from a positioning system.This may be accomplished by statistically analyzing characteristics ofthe signals communicated between the peering point server and thedevice. This methodology may improve a level of position accuracyobtained by a trace route between a model server and the device. Theimproved position accuracy may be within 5000 m of the true position ofthe device. In accordance with still another aspect, a method forcalibrating time and frequency references of a device whose position isto be determined is provided. The method includes calibrating the timeand frequency references through network communications between apeering point server and the device whose location is to be determined.This communication may occur over an asynchronous network. Thecommunication may be one-way, i.e. the peering point server maybroadcast communications to the device and from those communications thedevice may be operable to determine the proper time and frequencyreference or the communication between the device and the peering pointserver may be two-way. In one embodiment, the device may be in one-wayor two-way communication with a plurality of peering point servers toperform the calibrating step of the method.

In accordance with yet another aspect, the device may be operable toalign time and frequency elements in a receiver included in the deviceto the signal characteristics of a least one transmitter of thepositioning system. The signal characteristics to be aligned to may havebeen received by the device from a model server. This alignment, ortuning, in one embodiment may be to signals produced by the GPS system.

In accordance with an additional aspect, a method for receiving aplurality of signals from at least one transmitter of a positioningsystem is provided. The receiving of the signals may encompasscoherently integrating a signal over a period of time greater than about0.01 seconds, and incoherently integrating signals for proportionatelylonger periods. Generally, consumer grade GPS systems do not integratecoherently or incoherently over this long of a period of time. Theconsumer grade GPS systems generally rely on receiving stronger signalsto avoid the need for long integration. Additionally, consumer GPSsystems are typically mobile or handheld so longer integration times aredifficult to achieve since device movement may cause oscillator ortiming inaccuracies. In contrast, IP network attached devices aregenerally stationary and generally do not experience similarmovement-caused oscillator inaccuracies. The generally stationary natureof IP connected devices along with accurate signal characteristicdeterminations made by a model server may contribute to the ability ofthe device to integrate signals over a longer periods of time, includingtime periods if necessary longer than about 0.5 seconds.

In addition to extended acquisition times, additional embodiments mayprovide for methods where GNSS signal acquisitions may take place overan extended period of time. This is opposed to consumer grade GPSsystems, which generally must simultaneously receive enough signals todetermine a position fix from the simultaneously received signals. Incontrast, embodiments herein provide for a time-spread acquisition ofGPS signals. For example, a first satellite signal may be received attime A, and later second, third and fourth satellite signals may bereceived at a separate time B. The time-spread method disclosed hereinmay allow for the aggregation of the readings at separate times toestablish a position fix. The extent of time-spread may be more than onesecond. Since the GPS unit may remain stationary and a time referencemay be provided by a peering point server, under these circumstances thetime-spread may be more than one hour. In an additional embodiment, aplurality of signals necessary to create a position fix may all bereceived from a single satellite as it transits across the field of viewof the device. For example, in one embodiment, a signal may be receivedfrom a satellite in a first position and since the receiving device isprovided a time reference from a peering point server, a pseudo-rangefrom the satellite in the first position may be obtained. At a laterpoint, a second signal may be received from the same satellite but in asecond position. At the second time, a second pseudo-range may beobtained. Similarly, a third pseudo-range may be achieved when asatellite is in a third position. These three signals may then beaggregated to determine a position fix for the device, which hasremained stationary during the signal aggregation period.

In accordance with a further aspect, a method for determining theposition of a device relative to a fixed coordinate system based on atime calibration of the device and a plurality of received signals isprovided. Once signals have been received according to the methodsdescribed herein, and the received signals have been calibrated to thetime reference of the positioning system, calculations similar to thoseknown by those skilled in the art of positioning systems may be utilizedto determine a final position. This final position will generally beaccurate to within 50 m of the true position of the device and in manycircumstances may be far more accurate. Wherein as more signals may bereceived over time after the additional position fix, more accurateposition fixes may be possible. In this regard, an initial position fixmay have an accuracy within 200 m of the true position of the devicewhen combining network and satellite signal pseudo-ranges. In such acircumstance, continued acquisition of positioning system signals maylead to the position eventually being fixed to within an accuracy of 50m.

It is a further aspect of the current invention that the calculationsnecessary to determine a position fix may be performed by a model serveror other system in communication with the device over the computernetwork. According to this aspect, the device would transmit itsreceived satellite signals along with a timestamp or information as tothe accuracy of its clock at the time those signals were received to amodel server. The model server may then calculate, based on this data,the position of the device. The model server may then store thedetermined position in a database which correlates the device to itsdetermined position. In another embodiment, the calculations necessaryto determine a position may be performed at the device itself. In thisembodiment, the device may then report to the model server its positionand then the model server may record the device's position into adatabase. As noted earlier, the received satellite signals may be from asingle satellite that has transited across the field of view of thedevice or may be from multiple satellites.

In accordance with yet another aspect, a method is provided forreporting and electronically readable device identifier and devicelocation information for a device. In one embodiment, after the device'sposition has been fixed the device may store that position fix locally.In one embodiment when certain communications are initiated, such as anE911 call, the device may report its location to the recipient of thecall. In the case of an E911 call, the reporting of the location may beto the emergency call center that ultimately receives the E911 call. Inyet another aspect, when an E911 call is received by an E911 switch orcall center, the switch or call center may interrogate a databasecontaining location information for network-connected devices accordingto the present invention to learn the location of the device from whichthe E911 call was initiated. The call may then be promptly forwarded tothe proper emergency services dispatch center along with that locationinformation.

In accordance with still another aspect, a method of verifying apreviously determined position of a device connected to a network isprovided. This aspect of the present invention includes determining aposition of a device and gathering a first set of information regardingthe attachment of the device to a network. This first set of informationmay include information gathered by a peering point server in theprocess as described above of calibrating the time reference of thedevice to peering point server. The first set of information may alsoinclude information gathered in the IP trace route performed to gain aninitial estimation of the position of the device as described above. Inthis aspect, once a request for location information of the device hasbeen received, for example, the request may be generated during an E911call, the verification method may include generating a second set ofinformation containing the same type of information as the first set ofinformation and comparing the first set of information to the second setof information. If the comparison shows that a predetermined amount ofsimilarity exists between the two sets of information, the position ofthe device may be verified as being the same position as was previouslydetermined. This aspect of the invention allows for a quick verificationof the position of a device without going through a positioning systemsignal acquisition and calculation cycle. This aspect may also be usedto verify the position of devices at generally regular time intervals toensure that information within a location database is accurate. In oneembodiment, the information may include the packet mean time delaybetween the peering point server and the device. In another embodiment,the data may include the packet time delay distribution between thepeering point server and the device. In yet another embodiment, theinformation may include trace route information. The information mayinclude various combinations of the above-mentioned information types.

In accordance with an additional aspect, a method of selecting a processof determining the position of a device connected to a computer networkis provided. This aspect may include estimating a position of a deviceaccording to aspect previously discussed, obtaining data regardingcharacteristics of signals of a positioning system as discussed above,and attempting to receive signals based on the obtained data. Thisaspect further includes then determining the quality of a plurality ofsignals from the positioning system and, based on the determined qualitylevel, selecting between at least two methods of position determination.The first method may be where, as described above, the receiving deviceis calibrated to the positioning system time reference through thecomputer network. A second method may be where the time reference of thepositioning system is obtained from the positioning system itself. Thesecond process would be similar to those generally used by consumer GPSdevices wherein the need for an accurate time reference in the device isobviated by simultaneously acquiring multiple signals from thepositioning system.

In accordance with yet another aspect, a method of placing an E911 callis provided. In this aspect, an emergency telephone number is dialedfrom an IP device connected to an IP network wherein the IP device isoperable to receive signals from a positioning system such as the GPS.This is followed by connecting the IP device to the PSTN through the IPnetwork and then connecting through the PSTN to an emergency servicesnetwork and providing a location of the IP device to the emergencyservices network. This is followed by selecting an appropriate emergencyservices dispatch center based at least in part on the provided locationand transmitting the location information to the selected emergencyservices dispatch center and connecting the caller to that emergencyservices dispatch center. In one embodiment the interconnection betweenthe IP network and a switched network is through an IP network to PSTNgateway. In another embodiment the interconnection is made through amedia Gateway. In another embodiment the provision of the locationincludes interrogating an IP device location database and in stillanother embodiment, the provision of the location is accomplished by theIP device providing the location information directly to the emergencyservices network.

In accordance with a further aspect, a method for calculating a positionof an IP device attached to a computer network is provided wherein themethod includes receiving at the server over a computer network anindication from an IP device to initiate a location routine, performingand IP trace route between the server and the IP device to assist inestimating a position for the IP device, sending signal characteristicsto the IP device regarding characteristics of signals from a positioningsystem that may be incident on the IP device, receiving signals at theIP device from the positioning system, and calculating a position of theIP device based on the received signals.

In accordance with still another aspect, a method is provided fordetermining the position of a first device where an adequate positiondetermination may not immediately be made from the signals beingreceived at the first device. This aspect utilizes multiple devicesconnected to the same edge device of a computer network to make aposition determination. For example, a device on a first side of abuilding may only be able to receive signals from a single satellite anda second device in the same building but on an opposite second side maybe able to receive signals from multiple satellites. The current aspectof the invention would allow the signals received by the first andsecond device to be aggregated to produce a position determination whichwould generally approximate a midpoint between the two devices. Sincethe midpoint between these devices may be toward the center of thebuilding, the eventual location determination may be more accurate as tothe building itself, providing, for example, emergency service providerswith a more robust address determination.

In another aspect, an apparatus is provided that includes a networkinterface module, a signal receiving module, a frequency and timealigning module, and a timing module. The network interface module maybe capable of packetizing data and sending those packets over an IPnetwork and also to receive packetized data and reassemble the receivedpackets. The signal receiving module may be operable to receive signalsfrom a positioning system. The positioning system may be a GNSS systemsuch as, for example, the GPS. The frequency and time aligning modulemay be operable to obtain the frequency and time aligning informationover a connection to the network via the network interface module. Thetiming module may be operable to calibrate a time reference of theapparatus to an external time reference, where in the calibration isperformed over a network via communication through the network interfacemodule. In one embodiment, the apparatus includes a processing modulefor processing signals received by the signal receiving module in orderto determine a position of the apparatus. In another embodiment, theapparatus includes a barometric pressure sensor to assist in determiningthe altitude at which the device is located. In an additionalembodiment, the apparatus is a VODN unit. In yet another embodiment, theapparatus is a VoIP unit such as, for example, a VoIP phone.

In accordance with yet another aspect, a VoIP phone is provided whereinthe VoIP phone includes a voice conversion module operable to convertvoice to data and data to voice, a signal receiving module for receivingsignals from a GNSS such as the GPS, and a frequency and time aligningmodule for aligning the signal receiving module, a timing module forcalibrating the time reference of the VoIP phone to the time referenceof the GNSS, and a processing module for processing signals from theGNSS. In one embodiment of the aspect, the frequency and timeinformation used in the frequency and time aligning module is obtainedby the VoIP phone through a connection to a network via the networkinterface module.

In accordance with another aspect, a system for use in determining aposition of a device connected to a network relative to a fixedcoordinate system is provided. The system may include a device connectedto a network that is operable to receive signals from a positioningsystem, a model server in communication with the device over the networkand a peering point server in communication with the device over thenetwork. In this aspect, the model server may be operable to provide tothe device information regarding the signal characteristics oftransmitters of the positioning system and a peering point server may beoperable to calibrate the time reference of the device to a timereference of the positioning system. In one embodiment, the positioningsystem is a GNSS, such as the GPS. In another embodiment, the modelserver is operable to determine an estimate of the location of thedevice through communications with the device. In an additionalembodiment, the model server receives information from the deviceregarding the signals received by the device and from the signals isable to determine a position of the device. In yet another embodiment,the model server includes a database wherein a plurality of positionsare recorded correlated to a plurality of devices attached to thesystem. In one particular embodiment, the device is a VoIP phone. Inanother particular embodiment, the network is an asynchronous network.The asynchronous network may be an IP network.

Further areas of applicability of the present invention will becomeapparent from the detailed description provided hereinafter. It shouldbe understood that the detailed description and specific examples, whileindicating a preferred embodiment of the invention, are intended forpurposes of illustration only and are not intended to limit the scope ofthe invention.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and furtheradvantages thereof, reference is now made to the following DetailedDescription taken in conjunction with the accompanying drawings,wherein:

FIG. 1 is a schematic diagram illustrating a VoIP phone including asignal receiver module and network interface;

FIG. 2 is a schematic diagram illustrating a system of locating a deviceconnected to a network and receiving signals from a positioning system;

FIG. 3 is a flowchart for a method of determining position of a deviceconnected to a computer network relative to a fixed coordinate system;

FIG. 4 is a flowchart for a method of verifying a previously determinedposition of a device connected to a network relative to a fixedcoordinate system;

FIG. 5 is a flowchart for a method of selecting a process of determiningthe position of a device connected to a computer network relative to afixed coordinate system;

FIG. 6 is a flowchart for a method of placing a telephone call from anIP device connected to an IP network to an emergency services dispatchcenter;

FIG. 7 is a flowchart for a method of calculating a position of a deviceattached to a computer network;

FIG. 8 is a flowchart for a method of determining position of a firstdevice connected to a computer network relative to a fixed coordinatesystem;

FIGS. 9A and 9B are a schematic diagrams illustrating a system ofcalibrating time and frequency across an asynchronous network;

FIG. 10 is a schematic diagram illustrating a device operable to receivesignals from a positioning system and to receive time and frequencycalibration information across an asynchronous network;

FIGS. 11A and 11B depict a flowchart illustrating steps for determiningthe position of a device connected to a network;

FIG. 12 is a flowchart illustrating steps for updating a previouslydetermined position;

FIG. 13 is a flowchart illustrating steps for a start up process todetermine resource availability of a device;

FIG. 14 is a flowchart illustrating steps for determining the positionof a device using a time-spread method;

FIG. 15 is a flowchart illustrating steps for determining the positionof a device using a long baseline method; and

FIG. 16 is a schematic diagram illustrating a system of utilizingnon-simultaneously received calibrated signal measurements to determineposition.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, the invention is generally set forth inthe context of a Voice Over Internet Protocol (VoIP) device attached anInternet Protocol (IP) network receiving signals from the GlobalPositioning System operated by the U.S. military (GPS). Indeed, theinvention has a number of benefits and provides useful results in thisregard. However, it will be appreciated that various aspects of thepresent invention are not limited to VoIP devices, IP networkapplications or systems receiving signals from the GPS. Accordingly, thefollowing description should be understood as exemplary of the inventionand not by way of limitation.

The determination of the location of a device connected to a computernetwork is useful in many regards. To achieve this determination, adevice is provided herein that is capable of receiving signals from apositioning system and interfacing with a computer network. Aspects of adevice having such capabilities will be described along with variousnetwork resources to aid in the determination of the location of thedevice. Various methodologies describing the interaction of the devicewith the various network resources to achieve a determination of thelocation of the device will be illustrated. Also, detailed descriptionsof technical features will be provided.

FIG. 1 is a schematic diagram of one embodiment of a device (in FIG. 1the device is a VoIP phone 100) capable of interfacing with an IPnetwork 109 and receiving signals 111 from a positioning system (in FIG.1 the positioning system is represented by the GPS 110). The positioningsystem may be any system that transmits signals 111 that can then bereceived by the VoIP phone 100 and used to determine a location of theVoIP phone 100. Such a positioning system may be the GPS 110. Althoughin general, embodiments discussed herein will be described as receivingsignals from the GPS 110, it should be appreciated that otherpositioning systems may be utilized. For example, other GlobalNavigation Satellite Services (GNSS) systems such as those currentlyplanned to be deployed by the European Space Agency and Russian andJapanese governments may be used (Galileo, Glonass and QZSSrespectively). Alternatively or in conjunction with a GNSS system,ground-based transmitters could also be used.

The IP network 109, may be any computer network capable of linking theVoIP phone 100 to the remotely located elements of the positioningsystem described below. Of particular note is the system's ability tofunction while interconnected across asynchronous networks. Indeed, thesystem's ability to function using the Internet to interconnect variouscomponents of the system is of significant benefit. Although in general,embodiments discussed herein will be described as communicating over theInternet, it should be appreciated that the system is capable ofcommunicating over other types of computer networks and that the use ofthe Internet in the description should be considered exemplary and notlimiting.

In FIG. 1, the exemplary device is a VoIP device such as a VoIP phone100. Traditional communications over telephone lines utilize the PublicSwitched Telephone Network (PSTN). Phone calls made over the PSTNgenerally involve activating switches within the PSTN to provide adedicated circuit between the parties of the phone call. In contrast,the Internet is an IP network wherein information to be sent over thenetwork is divided into packets or packetized. A simplified sequence ofevents that take place during a phone call using a VoIP phone 100 may beas follows. Audio input, such as the speech of a caller is converted toelectrical energy by a microphone 107 contained within the VoIP phone100. This electrical energy will be in analog form and is converted intodigital form by an A/D converter 106. The digital signal may then bedivided and packetized by a network interface 101. Each packet of datawill contain information as to its destination. The packets of data arethen sent out over the IP network 109 wherein various routers will readthe destination information of the various packets and forward theinformation accordingly. Eventually the packets of information willarrive at a destination where they will be reassembled in their originalorder and converted to analog signals. The analog signals will be sentto a speaker (similar to speaker 108 of the VoIP phone 100) where theywill be converted to audio signals for the receiver of the call to hear.If the receiver is attached to the PSTN, a gateway will be requiredbetween the Internet and the PSTN to enable the Internet attached callerto communicate with the PSTN attached call receiver.

Although the device depicted is a VoIP phone 100, it should beappreciated that the device could be any network device including anyVoice Over Data Network (VODN) unit where it would be desired to knowthe location of the network device. For example, if the device wereleased or rented equipment, the lessor may wish to track the whereaboutsof that equipment and could do so using an embodiment as disclosedherein. Knowing the location of a computer attached the Internet couldassist users in searching for local resources such as doctors, stores,government offices, etc. Such a device could also be capable of alertingan owner or authorities of the location of the device if it were to bestolen and then connected to the Internet. The device could be a remotesensor, for example, a weather sensor or seismic sensor, in which casethe sensing data could be automatically correlated to the sensor'slocation.

A location determination module 113 may be included in the VoIP phone100. The module 113 may include a tuner module 102, a signal receivermodule 103, a timer module 104, and a signal processor module 105. Thelocation determination module 113 may contain circuitry and logic so asnot to disrupt the normal operation of the VoIP phone 100 since as willbe described shortly the location determination modules operate at timeswhen the VoIP phone 100 is not active in higher priority tasks, such asprocessing and trans-coding or translating voice packets. In this sense,the VoIP phone 100 would incorporate or “host” the locationdetermination module 113, as a subsidiary system which functionsexclusively as a location determination sub-system, using certain sharedhardware, interfaces, micro-processor, digital signal processor, memory,power supply and other circuit or logic elements appropriate to savecircuit replication cost where appropriate or desired.

The signal receiver module 103 may be operable to receive signals fromthe GPS. For simplicity and cost considerations, the signal receivermodule 103 may be a single channel receiver capable of tracking a singlesatellite at any given time. Alternatively, the signal receiver module103 may be a multichannel receiver capable of tracking two or moresatellites simultaneously. The signal receiver module 103 may include anantenna. The signal receiver module 103 may also filter incoming signalsas instructed by the tuner module 102.

The tuner module 102 may be operable to receive information regardingavailable satellite signals. The information may originate from anothersystem attached to the IP network 109 and be forwarded to the tunermodule 102 through the network interface 101. The information maycontain data regarding signal frequency, signal code phase, frequencyrate of change over time, navigation code bit state and bit timetransition. This information may then be used to enable the signalreceiver module 103 to lock on to the targeted signal.

Once a targeted GPS signal has been received, the signal may beprocessed by a signal processor module 105. The signal processor module105 may timestamp received signals, wherein the timestamp information isprovided by a timer module 104. This process is described in greaterdetail below. The VoIP phone 100 may then forward information related tothe received and timestamp signals to another system attached to the IPnetwork 109 for determination of the location of the VoIP phone 100.Alternatively, the signal processor module 105 may contain thecapability to determine the location of the VoIP phone 100 based onsignals received from the GPS and then send location data to othersystems over the IP network 109.

As shown, the tuner module 102, signal receiver module 103, timer module104, and signal processor module 105 together make up a locationdetermination module 113. In general, the location determination module113 has dedicated RF, signal filter, oscillator, and certain basebandhardware, interface circuits and software program logic, all of whichforms a remote GPS Pseudo-Range Capture Receiver (PRC) to measure knownincoming GPS signals and extract the pseudo-range time (that directlyrelates to time of flight from satellite to the receiving device).

Other components may be present in the VoIP phone 100. For example, asis typical with telephones, the VoIP phone 100 may include a numerickeypad for inputting numbers to be dialed and a display for displayingincoming or outgoing call information. A memory unit may also be presentto store user or device information or information related to thelocation determination process.

FIG. 2 illustrates a VoIP phone 100 as part of a system for use indetermining the location of a network-connected device as deployed in aprivate or public interconnected network. The VoIP phone 100 connects tothe packet data network through common IP network connections to thepublic Internet through one or more routers 202. The routers 202 may bea cascaded set. FIG. 2 shows a typical route between the end-device (theVoIP phone 100) and other peers or servers all similarly connected, andas such form a public IP access IP network 201, or Internet, as it isconventionally described in the art. As illustrated, the VoIP phone 100may also receive signals from the GPS represented by a satellite 110.

As noted above, the tuner module 102 of the VoIP phone 100 may receiveinformation regarding GPS signals which the VoIP phone 100 may attemptto receive. This information may come from a model server 205 attachedto the IP network 201. In general, there may be many individual modelservers 205 attached to the IP network 201 to provide the servicesdescribed herein. The functions described herein as being performed bythe model server 205 may all be performed by a single model server 205performing all the described tasks, or may be performed by severalindividuals specialized servers which together make up a model server205 as depicted herein. The ultimate number and configuration of serversneeded to perform the model server 205 functions will be dependent onthe number and distribution of devices requiring information from themodel server 205 and the number of functions having to be performed bythe model server 205.

The model server 205 may contain or have access to a variety ofinformation that enables the precise positioning of the VoIP phone 100.This information may include GPS satellite position data and GPSsatellite signal data. Also, model server 205 may also contain or haveaccess to a database that links components attached to the IP network201 with their physical locations. For example, the data may includerouter addresses and physical locations of those routers, the locationof other devices that have had their positions determined by the presentsystem, and information regarding characteristics of communications overthe IP network 201 with the VoIP phone.

The information regarding the location of routers and other devices thathave had their positions determined by the present system may be used bythe model server 205 to generate an approximation of the location of theVoIP phone 100. This can be accomplished by performing an IP trace toidentify routers used in communication between the model server 205 andthe VoIP phone 100. This process is described in detail below. Once ageneral location of the VoIP phone 100 is determined, the model server205 may determine the optimal satellite signals to be used by the VoIPphone 100 in the location determination process. This information isthen sent over the IP network 201 to the tuner module 102 of the VoIPphone 100 for use in tuning or calibrating the signal receiving module103.

As described above, the VoIP phone 100 may receive and timestampsatellite signals from the GPS. This information may then be forwardedto the model server 205 where it may be processed to determine thelocation of the VoIP phone 100. This arrangement allows the processingof the incoming pseudo-range and resulting location data to becentralized at the model server 205 and allows the end-devices whoselocation is to be determined to be of relatively limited function, whichmay reduce cost.

Once the location of the VoIP phone 100 has been determined, the modelserver 205 may place that information into a database. The informationwithin the database may then be accessed for a variety of purposesincluding the dispatching of emergency services to the location of theVoIP phone 100, law enforcement, or commercial Location Based Services(LBS). Access may be through a device, or interface, 210 directlyconnected to the model server 205 or through another device, orinterface, 211 in communication with the model server 205 through the IPnetwork 201. The model server 205 may also be operable to communicatewith a 9-1-1 switch 206 either directly or through the IP network 201.

As noted above, the VoIP phone 100 may timestamp signals received fromthe GPS. Similar to the reasoning described above in relation to thecentralization of the processing of location information by the modelserver 205, a time keeping function may also be centralized at a peeringpoint server 203. The function of the peering point server 203 may be tomaintain and disseminate timing information relative to the GPS.Generally, it is more efficient to synchronize remote devices over theIP network 201 when the devices to be synchronized are in physicalproximity. As a result, many peering point servers 203 may be positionedthroughout the physical area in which VoIP phones 100 are to have theirpositions determined. For example, to provide location information forVoIP phones 100 located in the United States, many peering point servers203, including possible multiple peering point servers 203 in aparticular metropolitan area, may be positioned throughout the UnitedStates.

The peering point servers 203 may be operable to disseminate timeinformation synchronized with the GPS. To do this, the peering pointserver 203 may be synchronized with GPS time. This may be accomplishedby an initial synchronization wherein subsequent synchronization withthe GPS is maintained with another high-stability reference such as anatomic clock 204. Synchronization between the peering point server 203and the GPS may also be accomplished through the reception of GPSsignals by the peering point server 203 or a GPS-referred timing deviceattached to the peering point server 203. In this case, a high-stabilityreference may serve as a backup time keeping system. Through methodsdiscussed in detail below, the peering point server 203 may synchronizewith the VoIP phone 100 through communication over the IP network 201.

To assist resolution of altitude and reduce the minimum number ofsatellite paths that must be recovered to establish a position fix,remote measurement of barometric pressure may be employed. In this case,the peering point server 203 may also include an atmospheric pressuresensor. Since the peering point server 203 may be placed in a fixedlocation of a known altitude, the atmospheric pressure sensor mayprovide a reliable baseline measurement to calibrate and offsetvariation in measured atmospheric pressure due to local atmosphericconditions. The measured pressure variation could then be used tocalibrate altimeters in proximity to the peering point server. The VoIPphone 100 may also be equipped with an atmospheric pressure sensor. Inview of the fact that the peering point servers 203 may generally be inproximity to the VoIP phone 100, peering point server 203 pressuremeasurements may be used to help determine the altitude at whichatmospheric pressure sensor equipped VoIP phones 100 are located. Thisprocess can differentially correct the air pressure readings toaccurately resolve VoIP phone 100 altitudes to within 3 to 5 metersbased on proximate peering servers, sampling and updates.

Traditionally, emergency calls such as 9-1-1 calls are routed throughthe PSTN 208 to a 9-1-1 switch 206. One function of the 9-1-1 switch 206is generally to route 9-1-1 calls to the proper emergency servicesdispatch center 209 for the location from which the call originated.Generally, this is done by referencing a database in which the PSTN 208telephone numbers are associated with locations. This PSTN database isgenerally maintained by the PSTN companies or service providers.However, one of the features of the VoIP phone 100 is that it can bemoved from Internet connection point to Internet connection point andstill function using the same telephone number. Therefore, the locationof the VoIP phone 100 is incapable of being maintained in the samedatabase using the same methods traditionally associated with the PSTN208.

Since, as described above, 9-1-1 switches 206 are generally connected tothe PSTN 208, emergency calls made from the VoIP phone 100 must berouted through a gateway 207 between the IP network 201 and the PSTN208. Since there may be no information regarding the VoIP phone 100 inthe PSTN database, the 9-1-1 switch 906 may interrogate a model server205 database, as described above, to determine the location of the VoIPphone 100. The communication between the 9-1-1 switch 206 and a modelserver 205 database may be a direct connection or an IP network 201connection. Alternatively, the VoIP phone 100 may transmit its locationinformation directly to the 9-1-1 switch once it has been connected.Once the 9-1-1 switch 206 obtains location information for the VoIPphone 100, it can then route the phone call from the VoIP phone 100 tothe proper dispatch center 209 along with corresponding locationinformation for the VoIP phone 100.

Although the above description is generally in the context of calling9-1-1 over a VoIP phone 100 attached to an IP network 201 and receivingsignals from the GPS, it should be appreciated that the scope of thisinvention is not limited to such components. That is the abovediscussion may apply to any network-attached device where the locationof the device is desired or a precise timing reference is desired.Similarly, any GNSS or terrestrial based system may be used by thesystem to determine the location of the network-attached device.Similarly, the system may function over any network and need not belimited to any particular IP network or the Internet.

FIG. 3 illustrates a methodology of determining the location of a deviceconnected to a computer network relative to a fixed coordinate system inan alternative implementation of the present invention. The illustrationis in the form of a flowchart wherein the first step is to estimate 301the location of a device relative to a fixed coordinate system to afirst level of accuracy by communicating over a computer network with amodel server. As in the previous illustrations, the present method willbe described generally in terms of a VoIP phone capable of receivingsignals from the GPS and communicating over the Internet. Also as notedabove, it should be appreciated that this is for exemplary purposes onlyand should not be interpreted as limiting the scope of the invention.

The device may be a VODN device capable of converting voice inputs intoa form capable of being transferred over a data network. The device maybe a VoIP device such as a VoIP phone wherein voice inputs are convertedinto data packets capable of being delivered across an IP network suchas the Internet. In general, devices such as VoIP phones will beconnected to an IP network through a broadband connection capable oftransferring at least 128 kbps bi-directional.

The computer network may be asynchronous or any network that uses packetdata communication techniques that lack explicit, inbuilt mechanisms totransfer a time or frequency to devices attached to the network.

The fixed coordinate system may be the coordinate system of a GNSS suchas GPS or GLONASS or a proposed GNSS such as Galileo or QZSS. The methodmay estimate a location relative to a single GNSS or apply signals frommultiple GNSSs. The coordinate system may also be a terrestrial basedsystem such as a localized system including, for example, multipleland-based “pseudo-lites”, or signals emanating from local transmissiontowers. The terrestrial based system may be GNSS synchronized. To aid inthe location process, the device may incorporate atmospheric pressuresensors to be used in determining the altitude of the device.

The estimation 301 may include a position task routine, where a traceroute sub-task is commenced. A trace route sub-task incorporates methodsknown to those skilled in the art to send a stream of User DatagramProtocol (UDP) or other packets to a known destination IP address overthe Internet. The purpose of the trace route is to identify allIP-addressable devices, typically routers that are between the sites. Asintermediate routers are encountered packets are designed to route backto the source while others continue toward the next router repeating theecho process with each intermediate router upstream from the source.Individual packets can be measured with each echoing intermediate returnfor the quality of the route as well as the round trip delay. The mainpurpose of this process is to inform the destination address, in thiscase a model server. The model server uses this information to search atleast one router database for a coarse geographical reference related tothe device. Those routers that are closest to the device are used toapproximate the device location. The searched router database may be acommercially available database containing routers and their physicallocations. The approximate location of the device based on thiscommercially retrievable reference error tolerance is quite large,30-100 kilometers, and may be deduced from previous trace routeoccurrences and database lookups.

The searched router database may also be a database created fromknowledge gained through repeated location determination of devicesaccording to the present method. For example, if a first device whoselocation is unknown is found to be directly connected to a router thatin turn is directly connected to a second device whose location isknown, the estimation uncertainty can be greatly reduced to generallyless than one kilometer.

Using trace route information, a coarse location of the device isestablished to a first level of accuracy. The next step is for thedevice to obtain 302 data over the computer network regarding estimatedsignal characteristics of the incoming GPS signals at the location ofthe device. That is, the appropriate signal model assistance parametersassociated with the physical location of the closest geographicallyidentified router to the end-device may be applied. The data is obtainedfrom a model server wherein the model server models and transfers to thedevice, following appropriate and conventional packet protocols, signalprocessing assistance information containing known satellite orbitalpositions (known in the art as ephemeris data) plus signal modulationinformation that reduces to message parameters the coded modulation andtiming characteristics emanating from as well as trajectory informationof each satellite.

Although in a present example, the positioning system is the GPS, itshould be appreciated that this is for exemplary purposes and anypositioning system may be utilized including terrestrial based systemsor GNSSs other than GPS, such as GLONASS, Galileo, and QZSS.

Specifically provided in the assistance data is each availablesatellite's Doppler, code-phase timing, navigation bit timing and bitstatus. Some or all of this data may be derived from commercial GNSSreference data suppliers (one exemplary source is RX Networks,Vancouver, BC Canada) designed to reliably deliver at near real-time,high accuracy satellite reference data parameters to sites around theglobe. In another embodiment, local reference stations that are locatedwithin the same country or region could supply this data. Since globaloperability is contemplated, global network operations centers may bepresent and essentially the same solution and data importationprocedures may be carried out in those centers around the world.

Also based on the estimation of the location of the device, the modelserver may assign an appropriate proximate primary and secondary peeringpoint server to facilitate the synchronization process described below.

Once an estimation for the location of the VoIP phone has beengenerated, the model server may provide the appropriate signal modelassistance parameters associated with the physical location of theclosest geographically identified router to the end-device. The modelassistance parameters will normally include orbital ephemeris data forsatellites in the field of view of the VoIP phone. For any particularsatellite in the field of view of the VoIP phone, the data may includesuch information as relative signal frequency (Doppler information),signal code phase, frequency rate of change, navigation code bit state,and a bit time transition event marker. The data may take into accountexpected Doppler shifting and other effects present at the estimatedlocation of the VoIP phone.

The model assistance parameters may vary in accuracy in relation to theaccuracy of the estimated location of the VoIP phone. For example, inthe case where the VoIP phone whose location is to be determined isattached to the same router as another device of known location, thesignal model assistance parameters may be generated under the assumptionthat the VoIP phone is within short distances, perhaps within tens orseveral hundred meters of the other device of known location. Under suchcircumstances, the signal model assistance parameters may be moreprecise than in a situation where the estimation process provides validestimates up to about 100 kilometers between the device and thereference site (e.g. the geo-referenced router).

The model server may also be capable of determining which satelliteswithin the field of view of the VoIP phone may be capable of providingthe most valuable location information. That is, when multiplesatellites are within the field of view of the VoIP phone, the modelserver may be capable of determining which satellite signal, ifreceived, would enable the most accurate location determination. Thisselection may also include selecting elements from various GNSSs orterrestrial systems.

The next step is to provide 303 at least one peering point serverattached to the IP network. The peering point servers, as previouslydescribed, may be synchronized with the GPS system and may be at leastfrequency and time referenced to each GNSS system. The next step is tocalibrate 304 a time and frequency reference of the VoIP phone with atime and frequency reference of at least one peering point server. Thisis accomplished through communications between the VoIP phone and atleast one peering point server over the IP network. Either the modelserver or the VoIP phone may initiate the calibration process betweenthe VoIP phone and at least one proximate peering point server. Onceinitiated, a calibration stream task launches precisely inter-departingpackets from the peering point server which are used to mark andsymbolize the transferred time interval to the remote device. Thistransmits the time and frequency reference packet stream across thenetwork segment from the peering point server to the remote receiverdevice, now bounded by the known IP addresses, verifying a common orstable route in both directions. This procedure also sounds the channelfor proper integrity testing. The receiver, e.g. VoIP phone, measuresthe streamed packet inter-arrivals in the remote receiver. As moresamples are gathered, the VoIP phone may test the statisticaldistribution formed by a large number of samples for integrity of thetransferred time and frequency process.

The results of these tests are then compared to distribution integritycriteria suitable to estimate the mean delay to within a suitable errorcriterion. If the criterion is not met, the process may be re-initiated.If the criterion is met, the next step may be to test for convergence,or the rate of increased estimation resolution of the mean referenceinterval delay based on the packet stream inter-arrival delay samples.If this falls within the criteria for appropriate rate of convergence,measurements of the refined mean delay are made. The same decision stepmay also trigger drawing the most current model server assistance data.

Once the refined mean interval is determined, assistance data frequencyand scaling information to create the proper reference clock referenceto calibrate the remote receiver is applied. The synchronization of aremote device with the peering point server over an asynchronous networkis an important aspect and is described in greater detail below. Theprocess may include passive calibration by the VoIP phone where thecalibration process is done solely through the reception of signals froma single peering point server. In another embodiment, the calibrationprocess may involve reception of calibration signals from multiplepeering point servers. In yet another embodiment, the VoIP phone may becalibrated through two-way communications between a single peering pointserver or multiple peering point servers.

By calibrating the VoIP phone to the peering point server which in turnis synchronized to the GPS, the VoIP phone may be calibrated to the GPS.This may eliminate the need to derive the time reference with the GPSfrom the GPS signals and therefore improve position performance orefficiency. The peering point servers may be synchronized with the GPStime through any means known to those skilled in the art. Methods ofsynchronization may include synchronization through reception of GPSsignals at the peering point server, equipping the peering point serverswith highly accurate timekeeping devices, or a combination of GPS signalreception and internal timekeeping. The peering point servers mayinclude, for example, an atomic clock capable of accuracy greater than100 ppb as measured against time reference of the GPS clock.

As noted above, the peering point servers may include pressure sensorsfor use in calibrating pressure sensors of VoIP phones in proximity tothe peering point servers. If so equipped, the peering point server maydetermine the local atmospheric pressure and use this information tocalibrate proximate VoIP phones containing pressure sensors. Thiscalibration information can then be used to determine the altitude of aVoIP phone.

The next step of the process illustrated in FIG. 3 is to align 305frequency and time elements of the VoIP phone to the signalcharacteristics of at least one of the GPS satellites as per the signalcharacteristics provided by the model server. The precision of thesignal characteristics provided by the model server is dependent on theaccuracy of the initial estimation 301. That is, the more accurate theinitial estimation 301, the more accurate the frequency and timeelements.

After the VoIP phone has aligned itself with expected frequency and timeelements emanating from at least one of the GPS satellites, the nextstep is to receive 306 signals being transmitted by at least one of theGPS satellites. The VoIP phone may initially attempt to receive a singlesignal emanating from a single GPS satellite. Alternatively, the VoIPphone may initially attempt to receive frequency and time elements ofmultiple signals emanating from multiple GPS satellites.

As noted above, the model servers may have provided an estimation of thesignals from the GPS system that should be incident on the VoIP phone.This relatively accurate estimation of signals combined with the mostlystationary nature of VoIP phones, allows for the VoIP phone to morenarrowly focus and dwell longer on a targeted GPS signal thanconventional mobile GPS devices. Stationary devices are not subject tothe same oscillator inaccuracies and drift as mobile devices experiencewhen the mobile devices are in motion. Generally, coherent integrationtimes of greater than 0.01 seconds can be utilized. If required, thecoherent integration time may be over a time period greater than aboutone half second. Accordingly, cumulative coherent and non-coherent timescan be similarly extended to increase sensitivity.

A common case is that the VoIP phone is located inside a building, wheretoo few simultaneously available satellite signals arrive to resolve apoint-position. Since the VoIP phones are normally not mobile (or in thecase of wireless, the access points are stationary), the VoIP phone mayreceive the signals necessary to fix a position over an extended periodof time. This method also allows improved accuracy by extendingobservation time to capture more satellites at different geometricalpositions to produce higher quality position fixes. The VoIP phone maycumulatively compile more time-spread measurements when as few as oneGNSS satellite signal is available per acquisition attempt. This processof compiling time-spread measurements may, for example, take place overa time period greater than about one hour. This process is described ingreater detail below. In the early stages of this process, it may bepossible to make a determination of a location to an intermediate levelof accuracy, wherein the intermediate level of accuracy is a levelbetween the original estimation based on the IP route trace, and a finallocation accuracy. The intermediate level of accuracy may be within50-200 m of the actual location of the VoIP phone.

The following step may be to determine 307 the position of the VoIPphone relative to the fixed coordinate system used by the GPS. Thisdetermination is made based on the received signals of the previous stepusing methods known to those skilled in the art. For example, since byvirtue of the calibration step, the time of flight of the signalsreceived from the GPS can be determined, and since the signals travel ata known rate, the distance between the GPS satellites and the VoIP phonecan be determined, thus leading to a position determination. Generally,GPS devices are capable of both receiving signals and making thecalculations necessary to translate those signals into a locationdetermination. In the present system, these functions may be separated.Both the VoIP phones and the model servers may have the capability toprocess the signal data received by the VoIP phones to make a locationdetermination using methods known to those skilled in the art.Alternatively, the signal processing capabilities may only be present inthe model server or only present in the VoIP phone.

After the position determination is made for the VoIP phone, anadditional step may be to report the VoIP phone position information.This reporting may be done to a database where such information isgenerally stored. This reporting may be to a component of a 9-1-1 callhandling system or it may be performed as part of connecting anemergency call from the VoIP phone to an appropriate emergency callcenter. The position determination information may also, oralternatively, be stored in the VoIP phone itself (after serverprocessing) so that the VoIP phone may provide this information. Thisinformation may, for example, be provided to an emergency servicesdispatch center during an emergency call. This information may also beprovided to other devices in proximity to the VoIP phone so that thosedevices may utilize or contain position information.

As noted above, the preceding description generally discussedembodiments in relation to a VoIP phone for exemplary purposes. Analternate embodiment may be where the device to be located is a wirelessdevice. In the case of a short-range wireless device, the position ofthe wireless access point used by that device may be used as theposition of the wireless device itself. Under these circumstances, thesteps described above would be performed at the wireless access point.Where the position of a wireless device may be ascertained relative toits corresponding wireless access point, a more accurate position of thewireless device may be obtained by combining the position informationfor the wireless access point and the wireless devices location relativeto that wireless access point.

FIG. 4 is a flowchart for a method of verifying a previously determinedposition of a device connected to a network relative to a fixedcoordinate system. The first step of this method may be to determine 401the position of a device relative to a fixed coordinate system. This maybe done according to the method described above in relation to FIG. 3.Alternatively, the position determination may be performed usingstandard GPS techniques. Indeed, the position determination can beperformed by any method known to those skilled in the art.

The next step may be to gather 402 a first diverse set of informationregarding the characteristics of the attachment to the network that areindicative of the attachment at the determined position. The set ofcharacteristics may include such characteristics as the mean time delayof data packets sent from a peering point server to the device, thedistribution of the time delay of data packets sent from a peering pointserver to the device, and trace route information between a peeringpoint server and the device. Together these characteristics form a“fingerprint” indicative of a unique connection to a network. Thesecharacteristics are then stored 403 for later retrieval. The storage maybe at the device, a peering point server, a model server, or any otherappropriate location.

The following step may be to receive 404 a request for locationinformation of the device. This request may be generated in a pluralityof ways. For example, a model server may generate such a request atregular time intervals to ensure the accuracy of information in adatabase which correlates devices to locations. The device itself maygenerate the request after a specific event, such as going through apower cycle. A third party or device may generate the request such as arequest by an emergency services dispatch center for the location of thedevice or a request by law enforcement officials for the location of thedevice.

Once the request has been generated, the next step may be to gather 405a second set of information regarding the same attributes gathered instep 402. This may be followed by comparing 406 the first set ofinformation to the second set of information. If the comparison resultsin surpassing a predetermined threshold of characteristic similarity,the position of the device may be verified 407 to be the originallydetermined position of step 401.

As described earlier, it is possible that embodiments of the presentinvention may take minutes or even hours to determine the position of adevice. In an emergency situation, it may be necessary to provideposition information immediately. The present method provides a processby which a previously determined position can be quickly verified and/ora database of positions can be kept updated using a minimal amount ofprocessor capacity (when compared to the process of determining aposition based on satellite signal acquisitions).

FIG. 5 is a flowchart for a method of selecting a process of determiningthe position of a device connected to a computer network relative to afixed coordinate system. The first step of this method is to estimate501 a position of the device relative to the fixed coordinate system toa first level of accuracy. This estimation is done by communicating overa computer network with a network operations center. The networkoperations center may have a database of locations of other devices onthe computer network. By tracing the communications between the networkoperations center and the device, the position of the device may beestimated based on known locations of devices present in thecommunications route between the network operations center and thedevice. The network operations center need not be a single computer orat a single location. Its function may be distributed between severalcomputers located at various locations.

The next step is for the device to obtain 502 data over the computernetwork regarding characteristics of a positioning system relative tothe estimate position of the device. This is followed by attempting 503to receive a plurality of signals of a positioning system. This isfollowed by determining 504 the quality of the plurality of signals ofthe positioning system.

The quality of signals may be placed into one of two broad categories.The first category is where the quality level of the signals is of ahigh enough quality level so that the device may within a reasonabletime gather enough signals from the positioning system to determine theposition of the device. Generally, this would mean that the device isable to acquire signals from four separate transmitters of thepositioning system generally simultaneously.

The second category is where the quality level of the signals is not ofa high enough quality to facilitate the generation of an accurateposition determination through the capture of multiple signalssimultaneously. Under these circumstances, the position determinationmay need to be made by gathering signals from the positioning systemover an extended period of time. This may be accomplished by calibratingthe time and frequency reference of the device as previously described.

Once the quality level of the positioning system signals has beendetermined, the next step is to select 505, based on the quality level,between determining position based solely on signals received by thedevice (in the case of the first category) and determining positionbased on signals received by the device and a calibrated time andfrequency reference (in the case of the second category).

FIG. 6 is a flowchart for a method of presenting a located call from anIP device, capable of receiving signals from a positioning systemconnected through an IP network, to an emergency services dispatchcenter. The first step of this method is to dial 601 an emergencytelephone number from an IP device connected to an IP network whichgenerates a call. “Dial” as used herein means any method known to thoseskilled in the art of initiating a phone call, including, but notlimited to, pressing 9-1-1 on a keypad, using a preprogrammed speed dialfeature or using a voice-recognition feature. The next step is toconnect 602 the IP device to a network interconnection capable ofinterconnecting an IP network to a PSTN. The connection between the IPdevice and the network interconnection is not a true connection in thesense that no dedicated line exists between the two devices. This partof the eventual link between the IP device and an emergency servicesdispatch center will be through the IP networking and hence be made upof packetized data transferred between the IP device and the networkinterconnection.

The network interconnection may be an IP network to PSTN gateway, amedia gateway, or any other interconnection known to those skilled inthe art. The network interconnection serves a function of receiving,ordering, and converting the packetized data from the IP device into ananalog signal capable of being transported across the PSTN. It alsoserves a function of packetizing the analog signal from the PSTN fortransport over the IP network to the IP device.

After the connection is established between the IP device and thenetwork interconnection, the IP device is connected 603 to an emergencyservices network attached to the PSTN. The emergency services networkmay be a 911 switch or other system for routing IP network calls toappropriate emergency service dispatch centers. The location of the IPdevice may then be provided 604 to the emergency services network. Basedon the location of the IP device, the emergency services network maythen select 605 an appropriate emergency services dispatch center. Theemergency services network may then transmit 606 the location of the IPdevice to the appropriate emergency services dispatch center and thenpresent the located call to the emergency services dispatch center 607.The order of presenting 607 and transmitting 606 may be reversed or mayoccur simultaneously.

The step of providing 604 the location of the IP device to the emergencyservices network may be accomplished in a variety of ways. For example,the emergency services network, upon receiving a communication from anIP device, may interrogate a database containing a correlation betweenIP devices and the locations of those IP devices. Another exemplarymethod is where the IP device itself provides its location to theemergency services network.

FIG. 7 is a flowchart for a method of calculating a position of a deviceattached to an IP network. The first step of this method may be toreceive 701, at a server, over an IP network a request, or position taskinvocation, giving an indication from a device attached to the IPnetwork to initiate a location routine for the device. The indicationfrom the device may be generated by, for example, the device beingplugged into a network connection or going through a power cycle.

Once the indication to start a location routine has been received, thenext step may be to perform 702 an IP trace route between the server andthe device. This IP trace route will return to the server a list ofintermediate servers between the server and the device. The server mayhave access to geographical information about the intermediate serversbetween the server and the device and from that information a positionof the device may be estimated 703. The server may have access toephemeris data for a GNSS system and be operable to send 704 signalcharacteristics of the GNSS system that may be incident at the estimatedposition of the device. The device may then align a signal receiver tothose signal characteristics, receive the GNSS signals and send thisdata to the server. Accordingly, the next step may be to receive 705from the device information about at least one signal from the GNSSsystem received by the device.

The server may then calculate 706 a position of the device based atleast in part on the signals received by the device. This informationcould then be sent back to the device so that the device itself cancontain its location information. The position information could be usedto populate a database. The database may be contained within the serveror may be remote from the server. If a position determination waspreviously made for the device, the task may be truncated, sinceoftentimes the device position will not have changed, as may be thecase, for example, where the location routine was initiated in responseto a temporary power loss at the device. Under such circumstances, thetruncated process may not include the step of performing 702 an IP traceroute.

FIG. 8 is a flowchart for a method of determining position of a firstdevice connected to a computer network relative to a fixed coordinatesystem. This method is referred to throughout this specification as thelong baseline method of position determination, wherein long baselinerefers to receiving signals at physically distinct locations andcombining the results from physically distinct locations and therebyimproving the quality of signals or geometry to include a fuller skyview. The first step of this method is to connect 801 a first device anda second device to an edge device of a computer network. Since the firstdevice and the second device are connected to the same edge device thereis a high probability that the first device and the second device willbe proximate to each other. For example, this may be the case where afirst VoIP phone and a second VoIP phone are attached to the same routerin an office building. Under such circumstances it is likely that thefirst VoIP phone and the second VoIP phone are within 200 m of eachother.

The next step may be to receive 802 at least one signal from apositioning system at the first device. For example, to continue theexample above, this may be where the first VoIP phone is able to receivesignals from only two satellites of the GPS. The next step may be toreceive 803 at least one signal from the positioning system at thesecond device. To continue the example above, this may be where thesecond VoIP phone is able to receive signals from two other satellitesof the GPS. In this situation neither VoIP phone on its own may becapable of determining a position. However, between the two VoIP phones,they are receiving four satellite signals which is generally enough todetermine a position. Therefore, the next step may be to estimate 804the position of the first device relative to the fixed coordinate systembased at least in part on a signals received by the first device andsignals received by the second device.

A position determined by the present method may not be as accurate as aposition determined where all the signals are received by a singledevice. However, the position determined by this method when generallyinsufficient signals are available at the first device would be moreaccurate than a position determination based only on signals received atthe first device. Returning to the example, two VoIP phones on oppositesides of a building may each be able to receive signals from two GPSsatellites. By combining the signals from these two devices a positionfix generally centered about the mid point between the two devices maybe obtained and may be of value in locating either one of the devices inan emergency situation.

Aspects described herein may be compatible with Industry StandardsInternet Engineering Task Force (IETF) which the North American NumberAssociation (NENA) designates as the so-called i2 and i3 referencediagrams and are incorporated herein by reference in their entirety. Thepurpose of the reference diagrams is to develop standard interfaceshaving data message and protocols that offer multi-vendor compatiblesolutions through open and physically distributed communications. Byconforming to these standards, or providing interfaces which conform tothese standards, embodiments described herein may be fully compatiblewith existing and future communication and location systems anddatabases.

The following sections of this detailed description describe in greaterdetail aspects of the communication between various elements discussedabove along with detailed descriptions of methods and apparatusesrelated to signal processing aspects.

FIG. 9A provides a schematic overview of methods of precise frequencyand time synchronization over asynchronous networks.

GNSS satellite 901 offers an exemplary source of high precision time,which is widely used to synchronize distributed communication,measurement and control systems. In this case the system uses satellitetime as a time transfer or time and frequency dissemination reference tocalibrate an end receiver 902. The GNSS signal 903 is received bypeering point server 904. The peering point server may include a highquality reception site with at least one external antenna and at leastone commercial reference receiver. GNSS signals may serve as a systemwide means to synchronize all such uniform packet generators within thepeering point servers 904. Individual packets 906 (three shown) areprecisely placed at a prescribed time interval, represented by the evenspacing along a time axis 907, associated with the known resources ofthe one-way channel between the peering point server 904 and the endreceiver 902.

As packets 909 transit across the open, interconnected IP network alonga routed network path 908, the reference time interval regularity isaltered due to interaction with other traffic transiting the IP network,and the packets 909 individually lose their original interval timeregularity due to the impact of shared traffic at the end receiver 902.Various strategies are known to those skilled in the art to overcome andcorrect for these time perturbations.

The random time interval fluctuations, or noise, first is recognizedwhen the packets are physically reconstituted, that is received,reassembled and validated by the end receiver 902. Multiple categoriesof time interval corruption arise depending on the level of contendingtraffic also transiting across some or all of the same network elementsas the measurement stream. Other factors include the available bandwidthof the interconnecting IP network segments, and the random electronicsignal fluctuations arising in all packet-handling elements. All but thelast effect impact the transit delay and inter-arrival interval across awide variation of possible transit and inter-arrival delays (as amultiple of the packet size plus inter-packet guard band time).

A disassembly and conditioning module 910 disassembles each packet andmarks its relative arrival time based on a local clock 914. Experimentaldata shows that the inter-arrival intervals can vary but are ascribedprimarily to two fundamental sources, contention delay due to backgroundtraffic and random jitter arising from each packet-handling device andtransmission device connected across a series circuit between thetransmitter and receiver. The disassembly and conditioning module 910can also use a sense of wide and narrow variation time-interval delay toreject the widely varying arrival samples presented to it, leaving thenarrowly varying random fluctuation intervals to be handled by a meanestimation and filter module 911, which determines the local “apparent”mean and associated variation about the mean. The wide inter-arrivaltime variations have a value several times the mean delay value(relative to a steady state value of transit delay) and are by virtue oftheir excess delay readily discriminated from the narrow variationsfound much closer to the mean time interval.

In recovering the mean time interval, the disassembly and conditioningmodule 910 acts as an adaptive filter, typical of those found in theart, first establishing a baseline interval delay from which a flexibleor fixed threshold accept/reject delay determination can accept orreject subsequent samples that exceed a threshold. The threshold is notchosen arbitrarily. It is chosen to avoid losing excess samples (networkemulation experiments show less than 5% of samples up to sustainedtraffic contention of 25% of system occupancy). It must also be set suchthat it does not contribute an excess statistical bias of many samplesof mean delay interval. The latter case based on experimental dataindicates that the random electronic jitter remains stable and isvirtually unaffected by the transient nature of packet contention andloss, that is the two effects are mutually independent mechanisms. Whilethe traffic loads can vary quite unpredictably, random “micro-jitter”variation remains stable and once filtered by the disassembly andconditioning module 910, leaves an expected superimposition of randomdelay to the mean estimation and filter module 911. Presenting the meandelay, plus the statistical inter-arrival delay variation to a remoteclock recovery and adherence module 912. This module 912 essentiallyprovides an accurate estimate of the mean delay by taking in all randomand mean samples and comparing the phase, or time advance or timeretarding values relative to the local clock 914.

This mean delay or error is then applied to a phase or frequency lockloop to then provide a scalable output frequency, from the end receiver902 which is proportional to the input voltage of the filter, creatingan output frequency. This output frequency is then divided by a knownamount and fed back to the phase comparator of the remote clock recoveryand adherence module 912. The difference in phase between the incomingand feedback divided replica of the voltage controlled oscillator, whichhas a frequency based on the local clock 914 is then brought intoconformance or agreement with the incoming packet signal. To reduceerror of the target precise time interval estimate, many incoming sampleintervals are applied to the feedback system. The exact number ofsamples is based on knowledge of IP connection channel, and thenecessary precision sought to meet a target stability and receiverintegration time. Evidence of stability is obtained from the errorsignal within the feedback system.

The filter output within the remote clock recovery and adherence module912 provides a signal fluctuation rate based on a fixed or adaptive timeconstants, which can be dynamically set. Filtering adaptively offersflexibility between setting the response of the feedback system forfaster convergence (typically desirable at the start of the convergenceprocess, when the transmit and receive errors are the greatest), andtaking more samples to shift a relatively steady state response (towardthe end of the process as the system approaches what could be describedas steady state or equilibrium).

The output frequency value and digitized bit stream signal at the outputof the remote clock recovery and adherence module 912 eventually reach apractical equilibrium value. This value practically means when theremote clock recovery and adherence module 912 output matches thetransmitted value to within a tolerable difference and thereforeprovides a usable reference value for calibrating or governing the endreceiver 902 at a precise value, which calibrates (or governs) frequencysynthesizer 913 as part of the end receiver 902 local oscillator locatedinside the GNSS Pseudo-range Capture (PRC) receiver 916. In oneembodiment, the feedback loop low-pass filter between the phase detectorand voltage controlled oscillator in the remote clock recovery andadherence module 912 offers a gauging or control signal 915. Thisprovides a conventional method of loop lock detection (among otherpossibilities, this could be implemented as a up/down value feedbackthrough a standard TCP/IP packet bearing control standard information).This detector and control message provide means to acknowledge lockstatus at the disseminating packet transmitter site, i.e. the peeringpoint server 904, so that signaling message values can be varied untilan out of lock decision threshold value is exceeded, which calls anewfor re-establishing the same end-to-end transmission and time/frequencytransfer process.

Receiver 916 adapts its remote receiver frequency synthesizer to thenetwork delivered frequency reference. The end receiver 902 is directedto dwell on prescribed satellite signal(s) 917 based on selectingassistance data described above. The precision of the reference definesone critical limit of reliably dwelling or integrating on selected GNSSmodulated signals (such as GPS L1, using CA coded signals) such that thefull coherent integration gain is obtained. The precision relates tocreating the longest coherent integration interval through the followingequation:f=1/(2*t)Where f=the frequency bandwidth uncertainty allowed within apre-designated frequency bin and t is the maximum coherent integrationinterval.

Other limits on the maximum coherent time interval are the stability ofthe receiver local oscillator and the uncertainty of predicting thesatellite Doppler frequency due to inexact coarse estimation of thereceiver position. Observing parallel, same-sized frequency bands, orfrequency “bins” allows a broader frequency uncertainty region to beobserved at once, which is a technique well established in the art tooffset these conditions. Maximum coherent integration time is also afunction of maximum oscillator drift, mostly induced by temperaturechanges. To control this effect the oscillator is either isolated fromenvironmental temperature gradients, or is precisely regulated using inthe art thermal sensing and compensation circuits or on-boardmicroprocessors and compensation algorithms, which adjust and correctthe oscillator frequency output even to very slight temperature changes.Using these methods known to those skilled in the art, the oscillatorfrequency output may be corrected to a degree that allows the highestsensitivity by extending coherent integration time. Finally, theoscillator must provide sufficiently low phase noise in order tomaintain coherent signal tracking. This factor is determined primarilyby the quality and cut of the physical crystal oscillator and suchoscillators are commercially available.

FIG. 9B depicts a schematic based on actual measurements of the generalcross-network transmission process in widely deployed IP networks, andthe impact of jitter on the packet stream transmission process. Jitterimpacts the network-transiting packets in very different ways. The firstand most pervasive are quiescent jitter mechanisms. These are randomdelay fluctuations, which appear and are most accurately observed at thereceiver physical ingress point. This point measures the arriving packettime intervals transiting electrically through intermediate active (e.g.switches, routers, repeaters, hubs) and passive (e.g. cable) networkelements. More elements add more delay variation, but the contributionto total variation is largely a function of the bandwidth capability ofthe devices. High bandwidth elements and segments predictably have lessrandom jitter than limited bandwidth segments and devices.

A precisely timed stream of packets 906 departs from a peering pointserver 904 at precise intervals. As packets transit a routed networkpath 908 the arrivals deviate from the original departure delays,appearing in the time domain as a near-Gaussian distribution 922 ofinter-arrival delays around an additional fixed transit delay 929relative to the original time of transmission 920.

Another level of jitter occurs when the interval-encoded packet streaminteracts with shared traffic transiting parts of the same network.These interactions are also random but create more pronounced delayssince they share the same transit time interval. Based on extensivephysical layer network measurements, these collisions result in apercentage of packets being deferred to later time intervals,illustrated in FIG. 9B as packet 919 is delayed outside an amountnormally associated with the Gaussian delay discussed above. Theexpected delay of packet 919 is shown in phantom 918. Under contendingpacket network traffic conditions, collisions occur, which is stronglymitigated but not eliminated by Collision Sense Multiple Access (CSMA)IP network protocols. The residual level of contending packet arrivalsare deferred by a readily discernable and much greater amount than therandom delay distribution that is experienced in the non-contendingcase.

These overlap contentions occur most routinely at shared routers orswitches which react by moving most shared, time-overlapping packets outto later, proximate time intervals. Under more extreme contentionsituations some packets will be lost. The deferred time intervals, basedon live network measurements, are found to be a strong function of thepacket size. The deferred packets experience contention delays that havea characteristic multi-state delay related to the fixed, repeatingpacket size and its time interval. The traffic-contention distribution923 shows the characteristic delay distribution, and outlying deferredcontention delays 924, 925.

When analyzing these two modes of packet jitter and resulting delayvariation, the original, fundamental delay state and delay variation,governed by the quiescent random fluctuations, is essentially unchanged.The outlying contention delays, shown schematically as harmonicallyrelated peaks 924, 925 are readily discriminated and rejected due totheir large distance from the fundamental delay state. The trafficsamples lost in these outlying delay states carry relatively fewsamples, and therefore lose relatively little information. Actualmeasurements on representative live networks show a modest 4% sampleloss with as much as 25% sustained contending traffic when measuringpacket delay variations over representative hop/route network segments.This also shows evidence of time-transfer resilience, little if anyincreases in mean estimation bias, and suggests a simple process ofrejecting outlying inter-arrival delays, delays mostly concentrated inthe contention peaks.

For completeness, a case 930 is shown where a stream is suddenly shiftedto an entirely different route during the streaming session. This routeshift superimposes a delay (relative to the previous delay distributions922, 923) such that the transiting traffic shifts to a longer networkpath (the analysis applies equally to longer or shorter routing cases).In this case, the longer route shifts the total path delay, and possiblythe random delay variation predictably. The pattern analysis process caneither track out to the new transit delay 931, or reject and restart thesession. The delay states provide a relatively unambiguous delay profileand thus allow the network packet delay measurement unit to berelatively straightforward to program.

Although described in terms of calibrating time and frequency over an IPnetwork using precisely timed packets, other forms of precise transferprotocols may be used. These protocols may be over local or wide areapacket data networks, either synchronous or asynchronous, and may bedesigned to supply synchronism to a network-connected device. Thesealternatives include using or enabling embodiments described herein withalternative, multi-application distributed time or frequency methodssuch as IEEE 1588, Pseudo wire, Circuit Emulation over Packet, or othercommercially available precision time and frequency disseminationmethods.

Embodiments described herein may also be operable to offer a commonprecise time and frequency synchronization through a common precise timetransfer method similar to that described in this invention. Embodimentsdescribed herein may also be operable to provide precise time and/orfrequency synchronism signals and services locally for applications suchas, but not limited to multi-media high definition video conferenceservices, video content and streaming, IPTV, audio content, audiostreaming, and point to point or multi-station conference telephonyservices that utilize synchronism to provide high qualitycommunications.

The communications between the peering point server 904 and the device902 may also be used to generate an improved estimate of the position ofthe device 902 prior to any receipt of signals from the positioningsystem. As discussed above, an IP trace route (between the device 902and a model server) may be used to determine the position of the device902 to a first level of accuracy. This first level of accuracy may bewithin 30-100 km of the true position of the device 902. In situationswhere no positioning system signals are readily available, theestimation of position to the first level of accuracy may be improved byanalyzing characteristics of the communications between the peeringpoint server 904 and the device 902. This process may include analyzingcharacteristics such as the communication times between the peeringpoint server 904 and the device 902 to estimate a distance between thepeering point server 904 and the device 902. Communications betweenmultiple peering point servers 904 and the device 902 may also be usedto assist in the position estimation process. This process may improvethe first level of accuracy, prior to any reception of signals from thepositioning system, to within 5000 m of the true position of the device902. In situations where signals from the positioning system are notimmediately receivable by the device 902, this improved first level ofaccuracy may at least allow for an emergency call placed from the device902 to be forwarded to the proper emergency services dispatch center forthe area in which the device 902 is located.

FIG. 10 illustrates the GNSS remote receiver stages that couple,amplify, filter, and down-convert GNSS in calibrated frequency alignmentwith the incoming GNSS signals.

The remote client receiver antenna 1001 couples the available RF signalsfrom GNSS satellites through a suitable Low-Noise Amplifier (LNA) 1002,of specifications that are commonly practiced for the purpose ofelevating signal to judicious levels to in part overcome the loss of RFfilter 1003. The RF filter 1003 provides a conventional bandpassresponse. It rejects spurious signals above and below a nominal centerfrequency of the GNSS frequency band. RF filter 1003 provides a firstorder immunity to high out-of-band interfering signals. This filteredsignal is then connected to a state of art RF mixer 1004 for furtheramplification and filtering, then in terms of the modulated signal isshifted down in frequency (“down-converted”) by conventionally mixingthe incoming GNSS signal with a device having a non-linear transferfunction, mixing the signal from the RF filter 1003 and the output offrequency synthesizer 1008. The non-linear mixing in the RF mixer 1004,presents two products at the output of the RF mixer 1004, one at adesired intermediate frequency (fIF), and the other at an “image” (thatis the signal product of the frequencies summed) frequency, which isrejected by conventional means such as filter 1005 ordinarily practicedin the art.

The intermediate frequency (IF) present at the output of the RF mixer1004 is a product of a superimposed set of incoming coded modulationGNSS signals. By standard design practices and methods, these are set tofall within a tailored IF channel bandwidth designed to be at least aswide as the highest excursion of GNSS carrier frequencies (offsetmaximally by their carrier Doppler shift due to satellite movementrelative to the remote GNSS receiver at a fixed ground position). Oncedown-converting the carrier to the IF, the final step is to suitablyfilter 1005 and amplify 1006, and then digitize the IF signal in ananalog to digital converter 1007.

This presents to the baseband processing and correlation stage 1009, aserially digitized signal to decompose the signal by recursivelyprocessing to then extract time-of-flight timing information from eachGNSS coded modulation signal available. The analog to digital converter1007 is designed to convert at sufficient speed to transfer optimalsignal energy to the baseband processor based upon minimizing samplingloss, while balancing the detail, or bit depth used to digitallyrepresent the analog IF signal.

To align the frequency synthesizer 1008 to the incoming signals, acorrected local clock reference output from a local clock 1011 is used.The local clock reference output is based on comparing in the localclock 1011 the difference between output 1014 from a remote receiverclock recovery module 1016 and output from a CDXO 1012. Remote receiverclock recovery 1016 clock recovery stage measures and estimates theprecise statistical mean delay of arriving packet signals. These signalsare physically sensed on connection 1017, which is a direct electricalconnection to the network media inside the protocol and interface stage1020 which is a conditioned electrical interface to the externalIP/packet data network connection 1021.

To increase sensitivity, the signal must sufficiently rise over thethermal noise occupying the same channel. A GNSS signal is such thatunder best reception conditions it arrives at a receiver no higher than14 dB below the noise power occupying the same channel. To reduce thenoise while maintaining the full information rate of the GNSS codedsignal, long term coherent processing gain may be utilized.

To increase the complex coded modulated products emanating from theanalog to digital converter 1007, a digital magnitude level 1030 andsign 1031 are connected to a complex mixer 1033 to form in-phase 1034and quadrature 1035 signals. These complex in-phase 1034 and quadrature1035 signals are connected to the complex correlators 1036, creatingin-phase 1037 and quadrature 1038 correlation products to an integrateand dump stage 1039. Integrate and dump stage 1039 is timed, based ontiming signal 1056 to integrate and then “dump” or decimate an output.The output of the integrate and dump stage 1039 represents thetime-integrated product of consecutive bipolar bit samples. Should theconsecutive bits result in a sufficiently net positive value over aselected integration period, the GNSS signal is deemed to be present atpower detector 1041. Samples can be concatenated and serially stored indata memory 1048 to extend sensitivity non-coherently or coherently.

If the frequency and time are precise, stable controlled in CDXO 1012,then the reference code phase and frequency will be a truer replica ofthe incoming signal. This can provide longer coherent correlationintervals. As well known in the art, coherent integration develops moresensitivity in a given observation period if the oscillator and otherdesign factors enable extension of the integration interval and thetarget frequency is sufficiently close to the true frequency, and thefrequency value can be tracked during integration to adjust thereference code appropriately.

Microprocessor 1050 provides routines for several functions. It managesthe search and acquisition process by managing the speed and detectionthreshold used to decide if the signal is deemed acquired withsufficiently low probability of error and should then be tracked (orre-acquired at certain time intervals) to continue measuringpseudo-range time samples. The acquisition or tracking modes control thesearch and lock 1046 and code-phase 1042 and frequency 4043 incrementtasks respectively. These increment or adjust at a rate deemedsufficient to generate new pseudo-range outputs at a specified designrate. This rate is balanced against the available processing resourcesavailable to perform more computations in a given period of time.Management and other programmable instruction are contained in a ROM1052 associated with the microprocessor 1050.

The microprocessor 1050 and programs running it are governed by theincoming assistance data module 1054. This readable memory registerbanks the incoming assistance data which are parameters based on currentsatellite status which in turn closely estimate the known available GNSSsignal frequency and code-phase and binary coded navigation message bitstate and time tag. Using this information, the closed loop receiveraims the receiver toward the likely precise frequency and searches thecode-phase with an appropriate number of parallel correlators in orderto seek, in reasonable time, the desired signal.

Another role for the microprocessor 1050 may be to draw and encodecurrent assistance data residing in the assistance data module 1054 oncedrawn from a model server 205. Parameter data is converted to a formthat is appropriate for regulating each parallel satellite signal searchand within each channel finely adjusting each target satellite searchprocess.

Another role for the microprocessor 1050 may be to measure carrier/noiseratio to provide model server 205 with current signal quality values inorder to refine estimated position confidence.

Another role for the microprocessor 1050 may be to extract and measurepseudo-range data from each acquired satellite signal either based onthe precision of the network disseminated clock information, via aprecise local time reference 1010 or multiple satellite observations,that following know methods in the art, resolve pseudo-range time byreference to a common satellite time base.

Another role for the microprocessor 1050 may be to forward measurementand related time tag data stored in memory in suitable message packetsfor transmission through a serial communication module 1019 onto the IPnetwork 201 and back to the model server 205.

This process may also be extended by searching for different satellitesignals in a parallel process by operating on different channels,exacting replicating channels formed by baseband processing andcorrelation stage 1009 for each target incoming coded signal. The searchprocess is one controlled within a closed loop formed by the basebandprocessing and correlation stage 1009 and microprocessor 1050 controlloop, which in turn control the incrementing values of the coarseacquisition (CA) epoch code-phase and Doppler offset frequency. Probablevalues of code-phase and relatively precise values of frequency will beknown and provided through the microprocessor 1050 and the serverarchitecture described in FIG. 2 prior to the search to optimally boundthe process.

The time and frequency management are enabled by import of the packetdata stream, which is brought across the IP/packet data networkconnection 1021 and remote receiver protocol and interface stage 1020.The focus of the precise time output 1013 from the remote receiver clockrecovery module 1016 is to regulate the receiver complex correlation andcode replication processes in order to enhance receiver sensitivity,which if done optimally will be mostly constrained by the stability ofCDXO 1012 oscillator.

Implementation of the baseband processing and correlation stage 1009 canbe accomplished in a plurality of ways, but for illustration purposesthe following conventionally practiced method is described using asoftware GPS system to exploit general-purpose Digital Signal Processing(DSP), such as Texas Instrument TMS320 family processors and IMAP orother suitable Real Time Operating Systems (RTOS) to use thecapabilities of these built in processing stages already existing incommercial VoIP and certain end-device IP equipment today. TexasInstrument's TNETV1060 family embeds the previously mentioned DSP andsupports baseband processing of GPS signals in a software-basedimplementation. The CDXO 1012, the remote receiver clock recovery module1016, and the connection 1017 are conventional elements of an enablingintelligent system that provides the memory and real time computationaland control processes to implement a hosted software implementation of abaseband processor.

The frequency and time synchronization services described in FIG. 10above can be served by either in- or out-of band packet data signalingand communication interfaces. All these service functions reside in theserial communication module 1019. This module 1019 also registers andmeasures signal pulses at the physical layer to more accurately marktime. This step provides enhanced precision by avoiding internal timingvariation imposed by registering time based on higher layer eventtiming. All the unit-timing functions are controlled through the output1014 from a remote receiver clock recovery module 1016 to ensuresynchronous operation in the client receiver logic.

FIGS. 11A and 11B depict a single flowchart illustrating the process ofpopulating a database with the location of an IP device starting from aninitial request to locate the device when the position of the device isnot known or assumed. For exemplary purposes the flowchart will bediscussed in terms of a VoIP phone attached to an IP network gatheringposition data from GPS satellites. It should be appreciated that othertypes of devices capable of being interconnected through a network andother positioning systems and their equivalents are within the scope ofthe present invention.

The first step is to invoke 1101 the position task routine. This taskmay be invoked by the VoIP phone after a particular event such as apower cycle, a reconnection to a network, or a change in theconfiguration of a local network. The VoIP phone obtains or haspre-stored destination IP addresses which initiate the trace route task.The task may also be invoked by the VoIP phone, peering point server ormodel server after a predetermined amount of time has gone by without averification of position. The next step is to perform a trace route 1102between the VoIP phone and a model server. The trace route 1102 may beinitiated by the VoIP phone upon start up. After the trace route 1102 iscompleted, the VoIP phone may send the results of the trace route 1102to the model server. The trace route 1102 may also be initiated by themodel server upon receiving a signal from the VoIP phone. In this case,the results of the trace route 1102 would be returned directly to themodel server.

The model server uses this information to search 1103 router database(s)for a coarse geographical reference, then applies 1104 the appropriatesignal model assistance parameters associated with the physical locationof the closest geographically identified router to the end-device. Themodel server then assigns 1105 the appropriate proximate primary andsecondary time/frequency servers to the VoIP phone whose location is tobe determined.

The next step is to initiate 1106 the calibration stream task to launchthe precisely inter-departing packets used to mark and symbolize thetransferred time interval to the remote device. This step is performedby the VoIP phone once a peering point server has been assigned 1105.The assigned peering point server then transmits 1107 the calibrationstream to the VoIP phone. The peering point server transmits 1107 thetime and frequency reference packet stream across the network segmentfrom the peering point server to the VoIP phone, now bounded by theknown IP addresses, verifying a common or stable route in one or bothdirections. This sounds the channel for proper integrity testing 1109.The receiver measures 1108 the streamed packet inter-arrivals in theVoIP phone. As more samples are gathered, the VoIP phone tests 1109 thestatistical distribution formed by a large number of samples forintegrity of the transferred time and frequency process.

The testing 1109 uses distribution integrity criteria suitable toestimate the mean delay to within a suitable error criterion. A decision1110 is made based on the results of the testing. If the criterion isnot met, the process is re-initiated falling back to step 1106. If thecriterion is met, the stream is tested 1111 for convergence, or the rateof increased estimation resolution of the mean reference interval delaybased on the packet stream inter-arrival delay samples. If this fallswithin the criteria 1112 for appropriate rate of convergence,measurements of the refined mean delay are made 1113. If this fallswithin criteria 1112, the VoIP phone will also send 1114 a request forthe most recent assistance data to the model server. The model serverwill prepare 1115 the most current assistance data and then send 1116that data to the VoIP phone.

Once the refined mean interval is measured 1113, the next step is toapply 1117 the assistance data frequency and scaling information tocreate the proper reference clock reference to calibrate 1118 the remotereceiver within the VoIP phone.

The next step is to initiate 1119 a standard remote receiver assistancetask and draw the current satellite assistance and time and frequencydata, and relevant satellite ephemeris and Doppler and navigation bitdata from the model server. This is done by the VoIP phone sending 1120a request for the most recent assistance data including satelliteephemeris and Doppler information to the model server. The model servercalculates 1121 the geographic reference with the most proximateassociation with the remote receiver device.

The model server calculates 1122 the model signals impinging on thelocale identified by the network geographic steps described above. Thisleads to reducing the model to signal parameters. This information isthen sent 1123 to the VoIP phone.

The VoIP phone then processes 1124 and translates the signal parameters,and applies 1125 the parameter data. The remote receiver within the VoIPphone may then acquire 1126 the targeted satellite vehicle (SV) signalor signals. From the acquired signals, pseudo-range measurements aremade 1127 for each SV. If the minimum number of quality pseudo-ranges toestimate a position fix have not been measured 1128, then the VoIP phoneinvokes 1129 a sparse set keep alive routine into which the receiverenters into an active state of occasionally scanning for new SV signals.Re-initiating 1119 does this based on model server data giving simplepredictions of opportune upcoming SV values that provide higherlikelihood of acquisition. The same process is repeated based on thescan for optimum signals based on future SV acquisition timing at theapproximate location. In some cases the signals will be tested a fewminutes later.

If the minimum number of quality pseudo-ranges to estimate a positionfix has been measured 1128, the VoIP phone may capture and store 1130the pseudo-ranges. Both pseudo-ranges (PR) and carrier to noise ratioinformation may then be forwarded 1131 to model server over networklink. The model server then calculates and establishes 1132 an estimatedposition, as well as the confidence level around the fix. Once theposition meets an estimated accuracy criterion, the next step is totransfer 1133 the location and VoIP phone information to a finishedlocation database. The information forwarded 1131 to the model servermay include the by-product of the opening trace route and time delaydistribution data. This data is stored 1133 as part of the location datafor the remote receiver. The estimated position may be transferred 1134from the model server to the VoIP phone for storing within the VoIPphone itself.

As noted above, a keep-alive process 1129 may be invoked. This processis illustrated the flow chart of FIG. 12.

This process may include regularly scanning the active status of theremote receiver, as well as invoking a position task (or often, ashorter re-check position case) based on event-driven criteria. Theevent driven criteria may include a test of power cycle change 1202, atest of network router or switch connection 1203, or a test of immediateconnection such as Ethernet or WiFi connection 1204.

Moreover, the keep-alive status register is programmed to routinelycheck 1205 position status regardless of event-driven status changes.Conditions designed to change states in steps 1202, 1203, 1204, and 1205are fed into the decision status step 1206. If the keep-alive and oneother event-driven register changed, decision step 1207 will order thereceiver to a dormant wait state 1201. If the receiver event-driven orkeep-alive status indicates a state change (e.g., disconnection ofdevice, loss of power, etc.) a test in decision step 1207 starts anexternal notification process.

The external notification process begins after an event driven change1207. The keep-alive status interval is communicated 1208 to a log keptin the proximate and backup peering point servers where the informationis logged 1209. When appropriate, and ordered by a processing centerhousing the model servers, the logged data is uploaded 1210 to a centraldatabase. The information is recorded 1211 in a location database whichwill generate an update order 1212 and send it to the VoIP phone basedon policy and other network management settings at the central point.The VoIP phone will then adjust 1214 the update cycle or leave it at thecurrent default setting.

FIG. 13 illustrates a start up process for the remote receiver of theVoIP phone to test availability of hosted, or shared, resources inend-devices where this configuration is used. Step 1301 initiates thepreviously described VoIP phone positioning task. To start thepositioning task, the receiver must acquire the shared digital signalprocessing and related memory resources of the host. A first step is todetermine 1302 if the digital signal processing (DSP) and microprocessorhost resources are available to perform a positioning task. If theresources are available the next step is to prepare 1303 themicroprocessor and perform a test of the memory map. If this test 1304results in a host interrupt status as being clear, the VoIP phone can beplaced in a ready status. This process tests the shared resources foravailability, and provides initialization of the resources to ensureintegrity. If the resources are unavailable as indicated by thedeterminations performed at step 1302 or step 1304, the process goes towait state 1306 called the await host processor interrupt clearindication. Once the resources are clear, the process can repeatstarting at the initiation 1301, and if the resources are available, theprocess can be terminated 1308 and the VoIP phone can be placed into aready status regarding the performance of a positioning task.

FIG. 14 depicts the process that exploits the time-spread observationfeature (discussed in detail below) to scan for selecting optimallyarriving signals in order to improve remote receiver position accuracy.The standard initial positioning task flow discussed above isundertaken. In the case where the receiver has posted a positionsolution to a first level of accuracy in the standard process, the VoIPphone may invoke 1430 a model server follow up task. The model servermay then choose 1404 one or more optimum SVs in positions to reducegeometric error using conventional and known orbital models for GPSsatellites. Optimal candidates are selected that minimize the geometricerror and form an assistance order which is sent 1405 to the VoIP phone.A simple decision step 1407 is taken to determine the sufficiency ofacquired signals to the criteria or policy limit. If the sufficiency isadequate, the VoIP phone processes the SV signals as described above andtransfers 1409 the signal data to the model server. The model serverthen updates 1410 the position record for the remote receiver. If thesufficiency is inadequate, the VoIP phone may retry SV acquisition up topolicy limits 1408.

FIG. 15 is a flowchart illustrating a process to achieve additionalsatellite signal availability and position accuracy using the longbaseline reception method previously noted. Long baseline receptionrefers to estimating position by combining observations from multipleremote receivers (such as multiple VoIP phones) all stationed in closevicinity, which is determined by the observation that they share acommon IP addressed router or switch device in a packet data network.The long baseline feature would typical apply to enterprise andinstitutional networks that have extensively deployed VoIP devices, allattached to a common router or switch.

The long baseline method combines measurements from dispersed receiversand in so doing accepts some error (when compared to an ideal receptioncase) arising from an unknown “baseline,” or intermediate networkconnection and distance between the receivers and the shared device.Thus, the long baseline inserts a physical distance error that is offsetby the value of combining observations to synthesize a value, leading toa more accurate estimated position compared to an individual receiver.In practice, the baseline is normally across a short distance (oftenless than 100 meters horizontally from a central position) and istolerable for the purpose of identifying the building street address ofthe remote receivers.

If during a previously described position identification process, it isdetermined that the receiver has insufficient satellite count orimperfect geometry-of-arrival pseudo-range measurements, a positioningtask taking into account the incomplete nature of the currentpseudo-range set may be initiated 1501. The next step may be to exhaust1502 the time-spread observation task. If the time-spread observationtask does not improve the quality of the position based on generalservice criteria, a query 1503 is initiated to find other remotereceivers connected and associated with the same router address. Ifother remote receivers are not present 1504, the device location isdefined as “less granular” and may be improved by another locationmethod 1505 and/or may be returned to the time-spread observation task.The granular location may then be forwarded to a location database withan indication of approximate position.

If other remote receivers are present 1504, the model server mayassociate 1506 the pseudo-range information of the other receivershaving a common router address. The combined pseudo-range information isthen tested 1507 computationally across two or more possible receiversalso commonly connected to the same router or switch to determineoptimal parameters for determining the position of the associateddevices. This optimization step is a computational task that takes intoaccount the geometry, signal strength, signal quality of the entireensemble of pseudo-ranges to find the best combined fix based on likelyredundant information. The next step is to apply 1508 different baselineseparation distances to generate more accurate estimates of the trueposition, scaling different baseline distance estimates. If the valuesconverge at a particular separation value, it is applied to all thevalues, which are then stored 1509 provisionally in a location database.The position determined using this method projects the apparentmulti-receiver position toward a central location (i.e., a point nearthe center of the subject building, which often translates to the streetaddress of the subject building).

The new position location estimate may be actively tested in one or moreof the long baseline linked receivers. This is accomplished by invoking1510 the common positioning task previously described, but with the newmore accurate position estimation as a result of the long baselineposition determination process to acquire target SV signals. If thisyields an adequate number of satellite signal acquisitions 1511, thepseudo-range data is then transferred 1513 to the model server.

If a sufficient number of the known SVs 1511 are still not observable,acquisition 1510 is retried until a program limit 1512 is met. If theprogram limit is met, but the position is less than fully resolved thisinformation is transferred 1513 to the model server along with anindication of the long baseline position task attempt. After thepseudo-range data is transferred 1513 to the model server, the locationin the location database is updated 1514. In the case where a positionwas updated even though a sufficient number of known SVs were notobservable, the process may revert back to the acquisition step 1510 tore-test the position for sufficient SV pseudo-ranges. This recursivestep is managed as a separate process with a distinct persistence re-trylimit.

The long baseline method described above is, for example, useful insituations where the receivers are situated inside buildings wheresatellite signal reception may be limited. Generally, devices thatoperate inside many corporate buildings require as much as 50 dB moresensitivity relative to a receiver designed to capture GNSS signals justoutside, so assistance and processing gain are essential to offsetin-building signal attenuation. Wood-frame houses are less lossy; bothsignal levels and simultaneous satellite reception levels are greaterthus enhance position fix accuracy. Generally, network-attached devicesmay be mobile or nomadic. In some cases, such devices will move betweenenvironments having different degrees of signal attenuation and thusreception challenge. As depicted herein, the devices housed insidebuildings will need to acquire signals at much lower levels than othertechnologies optimized for autonomous (handhelds) or mobile networkassisted devices.

The time-spread aspect mentioned above will now be described in greaterdetail. A common case where generally too few SV signals are availablefor a position fix using conventional methods is when the receiver isinside a building where too few simultaneously available satellitesignals arrive to resolve a point-position. Since network-connecteddevices contemplated are normally not mobile (or in the case ofwireless, the access points are stationary), this method substantiallyincreases the likelihood of resolving a location fix, especially incases where conditions prevent a minimum of four simultaneously acquiredsatellites, the traditional minimum observable number required toresolve a remote receiver device 3D position. An aspect of thisinvention is to allow more time to acquire weakened signals inapplications where the remote receiver is not moved over long timeperiods. This aspect also allows improved accuracy by extendingobservation time to capture more satellites at different geometricalpositions to produce higher quality position fixes. Another feature isto enable remote receivers to cumulatively compile more time-spreadmeasurements when as few as one GNSS satellite signal is available peracquisition session.

This method may also be used to extend the number of independent GNSSsignal measurements to further improve accuracy otherwise reduced byless than favorable signal levels, where there is less than optimalgeometry, where multi-path signal distortion is present, or in caseswhere dominant GNSS signal jamming masks weaker signals. These casesarise normally in the case of in-building located IP or VoIP devices,where such devices are either cable-connected inside a network plant, orare linked by a short range wireless access point and the access pointis stationary (and a position can be conferred based on the remotereceiver being embedded inside the wireless access point a shortdistance away).

By spreading time of observation, additional signal processing gain isgenerated relative to conventional “snapshot” acquisition receivers(wherein the devices may be pre-positioned).

To extend the receiver signal measurement time and not introduceexcessive errors, a key aspect is to control the value of remotereceiver oscillator or clock “bias” and record it and correct for it ateach GNSS signal acquisition event. Clock bias occurs where theoscillator is not calibrated at a known frequency, or it drifts at anunknown rate from a previously calibrated point, and thus generates anunknown time period offset relative to GNSS time. A conventionaltechnique is to use the acquired time of an extra satellite andcalibrate the other acquired signals to the extra satellite.

Such a bias or offset cannot be separated from the pseudo-rangemeasurement and estimation process since the bias introduces timecontraction or lengthening into the transit time measurement. To controlclock bias, the remote receiver time is registered, time stamped or“time-tagged” to values under a microsecond using the time/frequencydissemination system described above. Actual public network end-pointscan be measured from a peering point server designed for this purposefor round trip delay, and limit the actual GNSS time error as used bythe remote receiver to calibration values that are less than 100nanoseconds.

Biases of this small amount provide sufficient certainty of registeredtime accuracy at a remote receiver site to limit an individual pathdistance error attributable to oscillator clock bias to less than 30meters. As more geometrically diverse measurements are gathered, thecumulative effect of the individual measurement errors tend to diminishin the result based on the navigation model and subsequent calculationprocess.

Other than the bandwidth capacities of each network segment, the actualerror value will be a function of the numbers of router hops androute-segments between the remote end-point and an associated peeringpoint server. The values disclosed herein are representative of actualmeasurements using a representative number of hops and routes, andpeering point placements are chosen and otherwise suitably hop/routeconstrained to meet both commercial cost and network end-point coverageobjectives.

GNSS satellites constantly move providing new views, even of the samesatellite, and over time come into the field of view of quasi-fixednomadic, or permanently fixed remote receivers. As the satellites move,new opportunities arise to attempt capture of more satellite signals,which in turns provides additional system processing gain, which may beadded to coherent and cumulative non-coherent integration processinggain previously described. For perspective, variation in GNSS signallevels vary considerably inside buildings, as measured experimentallyfor GPS and direct satellite radio transmissions, signal levels can varyas much as 5-20 dB over a few minutes of time.

Conventional oscillators drift over time as much as 2-5 parts permillion and without correction would lead to pseudo-range measurementuncertainties as much as several hundred meters. To produce a position,each pseudo-range measurement is placed into a common reference frame.These paths in such a frame are denoted below as PR₁, PR₂, PR₃, . . .PR_(n), representing the measured transit time offsets for a particularsatellite signal based on that signal transiting between the satelliteand the user receiver, at a velocity of the speed of light. These arecalculated as follows:PR ₁=[(x ₁ −x _(u))²+(y ₁ −y _(u))²+(z ₁ −z _(u))²]^0.5+B _(t1)PR ₂=[(x ₂ −x _(u))²+(y ₂ −y _(u))²+(z ₂ −z _(u))²]^0.5+B _(t2)PR ₃=[(x ₃ −x _(u))²+(y ₃ −y _(u))²+(z ₃ −z _(u))²]^0.5+B _(t3). . .PR _(n)=[(x _(n) −x _(u))²+(y _(n) −y _(u))²+(z _(n) −z _(u))²]^0.5+B_(tn)Where a three-dimensional reference frame is defined by x, y, and zrepresenting three mutually orthogonal dimensions with a common originpoint. Where the numeric subscript identifies dimensional valuesassociated with each orbiting satellite vehicle orbital location, andusing a common reference frame containing the 3D locations of thesatellites and user location. Where the “u” subscript identifiesthree-dimensional values associated with the user receiver device. WhereB is the clock bias at a particular time plus or minus 3 ns per meter.

A geometric and linear algebra analysis is applied to resolve the userposition based on the individual path distances, a quantity deduced fromthe pseudo-range value, and the known dimensional values describing thetrue positions of the overhead satellites. This method is known to thoseskilled in the art. Current and granular satellite position is derivedfrom reference sources and delivered to a model server over eachinstance of time.

Clock bias subscripts t1, t2, t3 . . . tn refer to measured and recordedclock bias time error (recorded in a suitable time-tag message) which isassociated with the absolute time, or in the alternative a standardreference time offset, marking the time that this particularpseudo-range measurement was registered at the remote receiver. Thiserror value is used to eventually correct for the apparent time offsetrelative to zero clock bias error.

These distances are derived from a general equation of “coarse and fine”pseudo-range (PR) measurements, in the following manner:Whole PR Measurement (PR _(nT))=Coarse+Fine PR FactorsWhole PR Measurement=Z-Count+Number of Navigation Bits (times 20milliseconds)+Number of C/A code Epochs+Number of Whole C/A Code-phaseStates+Fraction of C/A Code-PhaseWhen directly measured using directly referenceable clocks at both endsof the transmission link, these terms can be condensed to:PR _(nT) =c(t _(u) −t _(sn))Where c equals the speed of light (2.98×10^8 meters per second), t_(u)equals the precise time of receipt of satellite n signal observed atuser receiver, and t_(sn) equals the precise time of departure of theemitted signal from satellite n. For highest path resolution, therelevant time is marked by a common reference modulation transition peakfound by correlating each satellite vehicle 1023-bit C/A code epoch, amethod capable of resolving to a small percentage of a code-phase bitwidth. Pseudo-range time measurements outside the above relativelysimplified notion of transit path distance measurement, are known tothose skilled in the art.

By way of the precise dissemination method described herein, the methodused tags each individual GNSS signal acquisition event, and in turnapplies an accurate error compensation value to each relatedpseudo-range measurement value. Among possible embodiments are toprovide at the end of each signal acquisition session a time markregistration or “time stamp,” that is referenced to a common,system-wide time standard, typically GNSS time, that can be used toeventually correct apparent pseudo-range measurement values into truerange values.

This time tag is resolved using the high precision time transfer methoddescribed herein. This method uses a statistical determination of timeinterval symbolized, encoded, and transmitted across the channel in astreaming packet session of fixed, known packet inter-arrivals, thendecoded. As mentioned above, this method also relies on judiciousplacements of the peering point servers so that they are relativelyproximate (but not to a critical degree) to a multitude of remotereceiver devices subtending each server's network domain. A typicalexample is one or two servers deployed per large metropolitan orregional area. In such a configuration, the time dissemination precisionand related remote device time uncertainty is readily held to manageablevalues.

Technical references found in the art demonstrate that high precisiontime transfer over the asynchronous network medium can be done and isvery useful to this field. Using a similar packet streaming measurementsignal and suitable time recovery methods which transfer timestampmessages using a round trip connection, these systems are able toachieve precision levels of errors less than 120 nanoseconds based ontaking frequent measurements.

FIG. 16 is a schematic representation of the transit time andmeasurement process. The focus is on the process of extracting and thencorrecting the remote receiver clock bias that is introduced overrelatively long time-spread signal observation intervals. The schematicis divided into two main sections. The real-time section 1600 representssatellite signals and measurements taken over an extended period of timewith the horizontal axis 1601 representing satellite time. The virtualsection 1623 is a schematic representation of how time-spreadobservations may be combined to produce a location determination.

At a time T1 a C/A epoch signal leaves a first satellite 1607 at aprecise time demarcated by a repeating sub-frame time containingnavigation bits, which contains precisely 20 such C/A epochs, and isrepresented by a time continuum of a first satellite 1607. In theschematic, the elements in the upper section 1605 pertain to thetransmission of signals by satellites and the elements in the lowersection 1606 pertain to the reception of the satellite signals by thereceiver. The signal is received by the receiver a short time after itis sent. This is represented by the offset from the first time T1 of theactual reception period 1608 of the signal from the first satellite1607. The distance between the actual reception period 1608 of the firstsignal and T1 is representative of the signal transit time. Each transittime varies in path delay, a value which depends on the true distancebetween the satellite and remote receiver position location at theprecise time of the signal receipt.

However, due to an internal clock inaccuracies or biases, the receivertimestamps the signal from the first satellite 1607 as being received asshown by the measured reception period 1610 for the first signal 1607.Since the receiver has been calibrated through contact with a peeringpoint server as per the previously described procedure, the receiver isable to timestamp or record the amount of offset 1609 present at T1. Inthis instance, the clock bias 1609 has resulted in the receiverperceiving and registering the measured reception period 1610 as beingreceived earlier than the actual reception period 1608.

Additional satellite signals come within the field of view and rise todetectable levels at T2. At T2, two satellite signals are received bythe receiver. Signal 1611 is transmitted from a second satellite andsignal 1612 is transmitted from a third satellite. The signals arereceived in satellite time at actual reception period 1613 for thesignal from the second satellite 1611 and actual reception period 1614for the signal from the third satellite 1612. The difference between thereception times 1613, 1614 is due to the different distances between thethird satellite and the receiver and the fourth satellite and thereceiver. However, due to internal clock inaccuracies or biases, thereceiver timestamps the signals from the second 1611 and thirdsatellites 1612 as being received as shown by the measured receptionperiods 1616, 1617, respectively. Since the receiver has been calibratedthrough contact with the peering point server as per the previouslydescribed procedure, the receiver is able to timestamp or record theamount of offset 1615 present at T2. Note that this offset is differentthan the offset that was present at T1. Through contact with the peeringpoint server the receiver is able to maintain its calibration relativeto satellite time.

Finally, at T3 a signal from a fourth satellite 1618 is received atactual reception period 1619. Again, due to internal clock inaccuraciesor biases the receiver timestamps the signal from the fourth satellite1618 as being received as shown by the measured reception period 1621.Note again that the offset 1620 has changed relative to its value at T1and T2 and has changed signs in that the measured reception period 1621is perceived as being received after its actual reception time.

Known GPS receivers, particularly consumer level receivers, generally donot have highly accurate timing capabilities and therefore requiresimultaneous reception of multiple GPS satellite signals to produce alocation determination. In such systems, the simultaneous acquisition ofmultiple GPS satellite signals obviates the need for highly accuratetiming capabilities. Such systems are incapable of making time-spreadposition determinations since any aggregation of time-spreadmeasurements would result in uncalibrated signal acquisition and eventssuch as depicted at 1626. In contrast, embodiments described herein areable to timestamp signal acquisitions by virtue of the calibrationfeature and therefore rebuild or calculate a complete set of correctedpseudo-range measurements 1625. From this complete set of pseudo-rangemeasurements 1625, an accurate position determination can be made fromsignals departing at a known time reference 1624.

Correcting all measurements using the method described herein takes eachuncorrected measurement 1610, 1616, 1617, 1621 and registers the localclock bias which is then compared to a local clock calibration valueprovided by disseminating time and frequency across the network (oralternatively, directly acts on the local oscillator by correcting theclock). The bias and contributing time offsets, shown as variations1609, 1615, 1620 are subsequently used to correct the remote receiveroscillator directly, adjust the value at the remote receiver, or sendthe correction value to the model server and applying it to the finalposition fix value rendered in the Model Server.

If the precise time reference of the GPS system is known, the exactdistance from each satellite from which a signal is received will beknown. For example, a signal from a first satellite informs a devicethat it is a fixed distance from the first satellite, which is at aknown point in space. This defines a sphere, wherein the device may beat any point on that sphere. A signal from a second satellite willdefine a second sphere. The intersection of the first and second spherewill form a circle wherein the device may be at any point on thatcircle. The signal from a third satellite will define a third sphere.The intersection of the first, second and third sphere will define twopoints in space. Generally, one of these two points will be at or nearthe surface of the earth and be used as a location fix for the GPSdevice. In this manner, a typical commercial GPS signal will be able toget a position fix once it knows its distance from three of the GPSsatellites. To know this distance, it must have an accurate timereference, and this is derived from a fourth satellite signal. Byperforming calculations on the four signals, a commercial GPS devicesable to derive the time reference and fix a position.

If, as in the embodiments described, the receiver has a time referencethat need not be derived from the satellite signal, it may make aposition fix with less received satellite signals. In other words,embodiments described herein may be able to make a position fix fromthree satellite signals. Moreover, if the embodiments described hereindo receive four satellite signals, the fourth signal can be used toenhance the accuracy of the position fix, so for any given number ofsignals present, embodiments described herein may produce a higheraccuracy position fix.

Additionally, embodiments described herein may use the earth as a thirdsphere and therefore only two satellite signals may be required to makea position fix. When using the earth as a third sphere, generally twopoints on the surface of the earth will be defined by the intersectionbetween the two satellite signals spheres and the earth sphere. In thiscase, the data derived from the IP network may be used to choose whichpoint is the receiver's location. Furthermore, the model servers maypossess topographical information regarding the surface of the earth toincrease the accuracy of a position fix wherein one of the spheres usedfor the fix is the surface of the earth. In this case, there may beerrors due to the assumption that the user is on the surface of theearth, as opposed to, for example, being in a high-rise building. Theremay also be errors due to inaccuracies in the topographical data.

As previously discussed, a highly accurate, locally calibrated,altimeter may be included in the receiver. Under these circumstances,the altimeter may accurately define a third sphere, which could be usedalong with two satellite signals and the router information to generatean accurate position fix. The use of the altimeter would eliminate theerrors discussed above related to inaccurate topographical informationor to the assumption that the user is at ground level.

As discussed above, a satellite signal need not be receivedsimultaneously when using the time-spread method. The time-spreadobservation method may be used to optimize network and systemefficiencies by reducing the number of time-spread observations demandedby a target error criteria or budget. While obtaining a position fix,the model server may direct the receiver to aim at particularsatellites, the reception of which would provide the most relevant dataregarding position fix accuracy. The signals may also be selected on thebasis of having the greatest joint likelihood of quality signalreception and greatest degree of position error mitigation both based ondilution of precision and calculations to make or rank candidatesignals.

In the event that a sufficiently precise time and frequency alignment isnot possible over the network to which the device is attached, the unitmay derive a position fix using methods generally used by consumer GPSreceivers as described above. In this regard, the model server mayprovide to the receiver satellite signal candidates most likely toprovide sufficiently strong signals from which to derive the timeinformation.

While various embodiments of the present invention have been describedin detail, it is apparent that further modifications and adaptations ofthe invention will occur to those skilled in the art. However, it is tobe expressly understood that such modifications and adaptations arewithin the spirit and scope of the present invention. It should also beappreciated that references contained herein to a device as being a VoIPphone should be considered exemplary and that any network-connecteddevice with position determining capabilities is included within thespirit and scope of the present invention. Also, the terms “receiver,”“remote receiver,” “end receiver” and “receiver” contained hereingenerally apply to the signal receiving module or portion of thenetwork-connected device. As noted above the network may be any of avariety of networks including asynchronous networks such as IP networks.Also as noted above, although the embodiments are generally described interms of receiving GPS signals, it should be appreciated that anypositioning system may be used and be within the spirit and scope of thepresent invention. These systems include other GNSS systems that may bedeployed currently or in the future along with current and futureterrestrial based positioning systems.

1. A method for determining position of a device connected to a computernetwork relative to a fixed coordinate system, said method comprisingthe steps of: estimating position of a device relative to a fixedcoordinate system to a first level of accuracy by communicating over acomputer network with a model server; obtaining, by said device, dataover said computer network regarding signal characteristics of apositioning system relative to said position estimated to said firstlevel of accuracy; providing at least one peering point server attachedto said computer network, wherein time and frequency references of saidat least one peering point server are calibrated to time and frequencyreferences of said positioning system; calibrating time and frequencyreferences of said device to said time and frequency references of saidat least one peering point server at least in part throughcommunications over said computer network between said device and saidat least one peering point servers; aligning time and frequency elementsin a receiver of said device to signal characteristics of at least onetransmitter of said positioning system, wherein said signalcharacteristics were acquired in said obtaining step; receiving aplurality of signals from said at least one transmitter of saidpositioning system, wherein said receiving step comprises (i) receivinga first signal of said plurality of signals from a first transmitterposition at said first point in time and (ii) receiving a second signalof said plurality of signals from a second transmitter position at asecond point in time, wherein said second point in time occurs at least1 second after said first point in time; and determining position ofsaid device relative to said fixed coordinate system to a second levelof accuracy based at least in part on said calibration and receivedplurality of signals, wherein said second level of accuracy is moreaccurate than said first level of accuracy, wherein said determiningstep comprises: a. determining, based on said first signal, a firstrange to said first transmitter position to define a first sphericalsurface centered at said first transmitter position; b. determining,based on said second signal, a second range to said second transmitterposition to define a second spherical surface centered at said secondtransmitter position; and c. combining said first signal and said secondsignal to determine said position of said device relative to said fixedcoordinate system to said second level of accuracy, wherein saidcombining comprises determining an intersection between said first andsecond spherical surfaces.
 2. A method as set forth in claim 1, whereinsaid computer network is an asynchronous network.
 3. A method as setforth in claim 2, wherein said computer network uses industry standardpacket communication protocols.
 4. A method as set forth in claim 2,wherein said computer network is an Internet Protocol (IP) network,wherein said calibrating step comprises calibrating time and frequencyreferences of said device to said time and frequency references of saidat least one peering point server at least in part throughcommunications over said IP network between said device and said atleast one peering point servers.
 5. A method as set forth in claim 4,wherein said device operates using Voice Over Internet Protocol (VoIP).6. A method as set forth in claim 5, wherein said device is a VoIPphone.
 7. A method as set forth in claim 4, wherein said computernetwork is the Internet.
 8. A method as set forth in claim 4, whereinsaid computer network is an intranet.
 9. A method as set forth in claim4, wherein said computer network is a wide area network.
 10. A method asset forth in claim 1, wherein said connection is a broadband connection.11. A method as set forth in claim 10, wherein said broadband connectionis operable to transfer at least 128 Kbps bi-directionally.
 12. A methodas set forth in claim 1, wherein said fixed coordinate system is a fixedcoordinate system used by a Global Navigation Satellite Services (GNSS)system.
 13. A method as set forth in claim 12, wherein said GNSS systemis the GPS.
 14. A method as set forth in claim 12, wherein said GNSSsystem is Glonass.
 15. A method as set forth in claim 12, wherein saidGNSS system is Galileo.
 16. A method as set forth in claim 12, whereinsaid GNSS system is QZSS.
 17. A method as set forth in claim 1, whereinsaid fixed coordinate system is a fixed coordinate system used byterrestrial based navigation system.
 18. A method as set forth in claim1, further comprising: performing an IP trace route for the routingbetween said model server and said device; and accessing at least onedatabase of positions of other devices on said computer network, whereinsaid estimating is based at least in part on a position of anotherdevice attached to said computer network present in said IP trace route.19. A method as set forth in claim 18, wherein at least one of said atleast one database of positions was developed by gathering data fromprevious performances of the present method.
 20. A method as set forthin claim 18, wherein at least one of said at least one database ofpositions of other devices is accessed by said model server through saidcomputer network.
 21. A method as set forth in claim 1, wherein saidfirst level of accuracy is within 100 km of said determined position.22. A method as set forth in claim 1, wherein said first level ofaccuracy is within 30 km of said determined position.
 23. A method asset forth in claim 1, wherein said estimation is based on the knownposition relative to said fixed coordinate system of an apparatusconnected to a router which is connected to said device.
 24. A method asset forth in claim 23, wherein said first level of accuracy is within200 meters.
 25. A method as set forth in claim 1, wherein saidpositioning system is terrestrial based system.
 26. A method as setforth in claim 1, wherein said positioning system is a GNSS system. 27.A method as set forth in claim 26, wherein said GNSS system is the GPS.28. A method as set forth in claim 26, wherein said GNSS system isGlonass.
 29. A method as set forth in claim 26, wherein said GNSS systemis Galileo.
 30. A method as set forth in claim 26, wherein said GNSSsystem is QZSS.
 31. A method as set forth in claim 26, wherein said datais obtained from at least one model server attached to said computernetwork.
 32. A method as set forth in claim 31, wherein said signalcharacteristics comprise estimates of one or more of the following:signal frequency, signal code phase, frequency rate of change over time,navigation code bit state, and bit time transition.
 33. A method as setforth in claim 1, wherein said positioning system is the GPS and saidtime and frequency references of said peering point server arecalibrated to time and frequency references of said GPS at least in partby reception of signals from said GPS.
 34. A method as set forth inclaim 1, wherein said peering point server maintains calibration withsaid positioning system at least in part by an internal timingreference.
 35. A method as set forth in claim 34, wherein said internalclock accuracy is greater than 100 parts per billion as measured againsttime reference of said positioning system.
 36. A method as set forth inclaim 1, further comprising the steps of: determining local atmosphericpressure; and calibrating a barometric altimeter located in said devicebased on said local atmospheric pressure.
 37. A method as set forth inclaim 1, further comprising the steps of: improving said first level ofaccuracy based on characteristics of said communications over saidcomputer network between said device and said at least one peering pointserver.
 38. A method as set forth in claim 37, wherein said originalfirst level of accuracy is poorer than 5000 meters and said improvingimproves said first level of accuracy to within 5000 meters.
 39. Amethod as set forth in claim 1, wherein said calibration is between saiddevice and a single peering point server of said at least one peeringpoint server, wherein said calibration is facilitated by two-waycommunication between said single peering point server and said device.40. A method as set forth in claim 1, wherein said calibration isbetween said device and a plurality of said at least one peering pointserver.
 41. A method as set forth in claim 40, wherein said calibrationis facilitated by two-way communication between said device and saidplurality of said at least one peering point server.
 42. A method as setforth in claim 40, wherein said calibration is facilitated by one-waycommunication from said device to said plurality of at least one peeringpoint server.
 43. A method as set forth in claim 1, wherein said step ofreceiving comprises integrating at least one of said plurality ofsignals over a time period greater than about 0.01 seconds.
 44. A methodas set forth in claim 43, wherein said step of receiving comprisesintegrating at least one of said plurality of signals over a time periodgreater than about 0.5 seconds.
 45. A method as set forth in claim 1,wherein said positioning system is a GNSS system wherein said step ofreceiving comprises acquiring said plurality of signals over a timeperiod of at least about 1 second, wherein signals received during any 1second period of time during said time period of at least about 1 secondare insufficient to determine a position of said device.
 46. A method asset forth in claim 1, wherein said positioning system is a GNSS systemwherein said step of receiving comprises acquiring said plurality ofsignals over a time period greater than about 1 hour, wherein signalsreceived during any 1 hour period of time during said time periodgreater than about 1 hour are insufficient to determine a position ofsaid device.
 47. A method as set forth in claim 45, wherein saidpositioning system is a GNSS system, wherein said step of receivingcomprises acquiring said plurality of signals from one satellite of saidGNSS system.
 48. A method as set forth in claim 1, wherein said secondlevel of accuracy is within 50 meters.
 49. A method as set forth inclaim 1, wherein said determination further comprises determiningposition of said device relative to said fixed coordinate system to athird level of accuracy based at least in part on said calibration andreceived plurality of signals.
 50. A method as set forth in claim 49,wherein said second level of accuracy is within 200 meters.
 51. A methodas set forth in claim 49, wherein said third level of accuracy is within50 meters.
 52. A method as set forth in claim 1, wherein calculationsnecessary to achieve said determination are performed by a module thatis a part of said device.
 53. A method as set forth in claim 1, whereincalculations necessary to achieve said determination are performed by amodule that is not a part of said device and is connected to saidcomputer network.
 54. A method as set forth in claim 53, wherein saidcalculations are performed by said model server.
 55. A method as setforth in claim 54, further comprising the step of: storing saiddetermined position in a database.
 56. A method as set forth in claim 1,wherein said comprises receiving a plurality of signals from a singletransmitter of said positioning system.
 57. A method as set forth inclaim 1, wherein said determining consists of receiving a plurality ofsignals from a plurality of transmitters of said positioning system. 58.A method as set forth in claim 1, wherein said method further comprises:reporting from said device position information for said device based onsaid determined position.
 59. A method as set forth in claim 58, whereinsaid reporting is over said computer network.
 60. A method as set forthin claim 1, wherein said reporting comprises reporting an electronicallyreadable device identifier and device location information for saididentified device.
 61. A method as set forth in claim 60, wherein saidreporting is to an emergency call center.
 62. A method as set forth inclaim 1, wherein said device is a wireless access point.
 63. A method asset forth in claim 62, wherein a wireless device in communication withsaid wireless access point reports its position to be that of thewireless access point.
 64. A method as set forth in claim 62, wherein awireless device in communication with said wireless access point:determines its location relative to said wireless access point; anddetermines its position relative to said fixed coordinate system basedon said wireless access point position and said location relative tosaid wireless access point.
 65. An apparatus comprising: a networkinterface module; a signal receiving module that receives signalstransmitted by at least one transmitter of a positioning system, whereinsaid signal receiving module receives a first signal from a firsttransmitter position at a first point in time and a second signal from asecond transmitter position at a second point in time, wherein saidsecond point in time occurs at least 1 second after said first point intime; a frequency and time aligning module for aligning said signalreceiving module, wherein said frequency and time aligning module isoperable to obtain frequency and time aligning information regardingsaid positioning system over a connection to a network via said networkinterface module; a timing module, wherein said timing module isoperable to calibrate a time reference of said apparatus with a timereference of said positioning system over a connection to said networkvia said network interface module; and a processing module, wherein saidprocessing module: (i) estimates a position of said apparatus relativeto said positioning system to a first level of accuracy by communicatingover said computer network; (ii) determines, based on said first signal,a first range to said first transmitter position to define a firstspherical surface centered at said first transmitter position; (iii)determines, based on said second signal, a second range to said secondtransmitter position to define a second spherical surface centered atsaid second transmitter position; (iv) determines an intersectionbetween said first and second spherical surfaces; and (v) determines aposition of said apparatus relative to said positioning system to asecond level of accuracy based at least in part on said calibration anda combination of said first signal and said second signal, wherein saidsecond level of accuracy is more accurate than said first level ofaccuracy.
 66. The apparatus of claim 65, wherein said apparatus is avoice over data network unit.
 67. The apparatus of claim 65, whereinsaid apparatus is a VoIP unit.
 68. The apparatus of claim 65, whereinsaid apparatus is a phone.
 69. The apparatus of claim 65, wherein saidnetwork interface module is capable of interfacing with an IP network.70. The apparatus of claim 65, wherein said positioning system is aGNSS.
 71. The apparatus of claim 70, wherein said GNSS is the GPS. 72.The apparatus of claim 65, further comprising a barometric pressuresensor.
 73. A Voice Over Internet Protocol (VoIP) device comprising: avoice conversion module that converts voice to data and data to voice; anetwork interface module; a signal receiving module that receivessignals transmitted by at least one transmitter of a GNSS, wherein saidsignal receiving module receives a first signal from a first transmitterposition at a first point in time and a second signal from a secondtransmitter position at a second point in time, wherein said secondpoint in time occurs at least 1 second after said first point in time; afrequency and time aligning module for aligning said signal receivingmodule, wherein said frequency and time aligning module is operable toobtain frequency and time information regarding said GNSS over aconnection to a network via said network interface module; a timingmodule, wherein said timing module is operable to calibrate a timereference of said apparatus with a time reference of said GNSS over aconnection to said network via said network interface module; and aprocessing module for processing signals received by said signalreceiving module, wherein said processing module: (i) estimates aposition of said VoIP device relative to said GNSS to a first level ofaccuracy by communicating over said network; (ii) determines, based onsaid first signal, a first range to said first transmitter position todefine a first spherical surface centered at said first transmitterposition; (iii) determines, based on said second signal, a second rangeto said second transmitter position to define a second spherical surfacecentered at said second transmitter position; (iv) determines anintersection between said first and second spherical surfaces; and (v)determines a position of said VoIP device relative to said GNSS to asecond level of accuracy based at least in part on said calibration anda combination of said first signal and said second signal, wherein saidsecond level of accuracy is more accurate than said first level ofaccuracy.
 74. The VoIP device of claim 73, wherein said GNSS is the GPS.75. A system for use in determining a position of a device connected toa network relative to a fixed coordinate system, comprising: a deviceconnected to a network, wherein said device receives signals transmittedby at least one transmitter of a positioning system, wherein said devicereceives a first signal from a first transmitter position at a firstpoint in time and a second signal from a second transmitter position ata second point in time, wherein said second point in time occurs atleast 1 second after said first point in time; a model server incommunication with said device over said network, wherein said modelserver is operable to provide to said device information regardingsignal characteristics of said transmitters of said positioning system;a peering point server to communicate with said device over saidnetwork, wherein said peering point server is operable to calibrate oversaid network a time reference of said device to a time reference of saidpositioning system; and a processing module for processing signalsreceived by said device, wherein said processing module: (i) estimates aposition of said device relative to said positioning system to a firstlevel of accuracy by communicating over said network; (ii) determines,based on said first signal, a first range from said device to said firsttransmitter position to define a first spherical surface centered atsaid first transmitter position; (iii) determines, based on said secondsignal, a second range from said device to said second transmitterposition to define a second spherical surface centered at said secondtransmitter position; (iv) determines an intersection between said firstand second spherical surfaces; and (v) determines a position of saiddevice relative to said positioning system to a second level of accuracybased at least in part on said calibration and a combination of saidfirst signal and said second signal, wherein said second level ofaccuracy is more accurate than said first level of accuracy.
 76. Thesystem of claim 75, wherein said positioning system is the GPS.
 77. Thesystem of claim 75, wherein said model server is operable to determinean estimate of the location of said device.
 78. The system of claim 75,wherein said model server comprises a database correlating a pluralityof devices to a plurality of corresponding locations.
 79. The system ofclaim 75, wherein said device is a VoIP phone.
 80. The system of claim75, wherein said network is an asynchronous network.
 81. The system ofclaim 80, wherein said asynchronous network is an IP network.
 82. Amethod as set forth in claim 1, wherein said calibrating step calibratessaid time reference of said device to within 120 nanoseconds of saidtime reference of said at least one peering point server.
 83. A methodas set forth in claim 1, wherein said device is a wireless access point,wherein the method further comprises: determining a location relative tosaid wireless access point of a wireless device in communication withsaid wireless access point; and determining a position of said wirelessdevice relative to said fixed coordinate system based on said wirelessaccess point position and said location relative to said wireless accesspoint.
 84. A method as set forth in claim 1, wherein said device is aVoIP phone.
 85. A method as set forth in claim 1, wherein said secondpoint in time occurs at least 1 hour after said first point in time. 86.A method as set forth in claim 4, wherein said positioning system is aGNSS system wherein said step of receiving comprises acquiring saidplurality of signals over a time period of at least about 1 second,wherein signals received during any 1 second period of time during saidtime period of at least about 1 second are insufficient to determine aposition of said device.
 87. A method as set forth in claim 86, furthercomprising: performing an IP trace route for the routing between saidmodel server and said device; and accessing at least one database ofpositions of other devices on said computer network, wherein saidestimating is based at least in part on a position of another deviceattached to said computer network present in said IP trace route.
 88. Amethod as set forth in claim 87, wherein said device is a wirelessaccess point, wherein the method further comprises: determining alocation relative to said wireless access point of a wireless device incommunication with said wireless access point; and determining aposition of said wireless device relative to said fixed coordinatesystem based on said wireless access point position and said locationrelative to said wireless access point.
 89. A method as set forth inclaim 87, wherein said device is a VoIP phone.
 90. A method as set forthin claim 4, further comprising: performing an IP trace route for therouting between said model server and said device; and accessing atleast one database of positions of other devices on said computernetwork, wherein said estimating is based at least in part on a positionof another device attached to said computer network present in said IPtrace route.
 91. A method as set forth in claim 90, wherein said deviceis a wireless access point, wherein the method further comprises:determining a location relative to said wireless access point of awireless device in communication with said wireless access point; anddetermining a position of said wireless device relative to said fixedcoordinate system based on said wireless access point position and saidlocation relative to said wireless access point.
 92. A method as setforth in claim 90, wherein said device is a VoIP phone.
 93. A method asset forth in claim 92, wherein said calibrating step calibrates saidtime reference of said VoIP phone to within 120 nanoseconds of said timereference of said at least one peering point server.
 94. The apparatusof claim 65, wherein said timing module calibrates said time referenceof said apparatus to within 120 nanoseconds of said time reference ofsaid positioning system over said connection to said network.